summaryrefslogtreecommitdiffstats
path: root/clang/lib/CodeGen/CodeGenModule.cpp
diff options
context:
space:
mode:
authorArgyrios Kyrtzidis <akyrtzi@gmail.com>2012-03-30 00:19:18 +0000
committerArgyrios Kyrtzidis <akyrtzi@gmail.com>2012-03-30 00:19:18 +0000
commitab468b03815a8454b4bda1e5b4f20bc1ad7f1857 (patch)
treee29bfdd4f890c99cb9b15e7d5d5af99dbb16e76a /clang/lib/CodeGen/CodeGenModule.cpp
parentc9754d6d9c53a93252544a95fb48eb98b8c44217 (diff)
downloadbcm5719-llvm-ab468b03815a8454b4bda1e5b4f20bc1ad7f1857.tar.gz
bcm5719-llvm-ab468b03815a8454b4bda1e5b4f20bc1ad7f1857.zip
Add info to ObjCPropertyRefExpr to indicate whether the dot syntax property
reference is going to message the setter, the getter, or both. Having this info on the ObjCPropertyRefExpr node makes it easier for AST clients (like libclang) to reason about the meaning of the property reference. [AST/Sema] -Use 2 bits (with a PointerIntPair) in ObjCPropertyRefExpr to record the above info -Have ObjCPropertyOpBuilder set the info appropriately. [libclang] -When there is an implicit property reference (property syntax using methods) have clang_getCursorReferenced return a cursor for the method. If the property reference is going to result in messaging both the getter and the setter choose to return a cursor for the setter because it is less obvious from source inspection that the setter is getting called. The general idea has the seal of approval by John. rdar://11151621 llvm-svn: 153709
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud