The isPointer matcher is useful for http://reviews.llvm.org/D15623.
Details
Diff Detail
Event Timeline
include/clang/ASTMatchers/ASTMatchers.h | ||
---|---|---|
3558 | Sorry for the delay in review. Would be interesting to get an example that is different between isAnyPointerType and isPointerType. |
include/clang/ASTMatchers/ASTMatchers.h | ||
---|---|---|
3558 | The definitions of Type::isAnyPointer() is: return isPointerType() || isObjCObjectPointerType(); Is there a straightforward way to test objc code in these unit tests? If not I can also remove the isAnyPointer() matcher. |
include/clang/ASTMatchers/ASTMatchers.h | ||
---|---|---|
3558 | We already have some obj-c tests (see line 932 for example) |
include/clang/ASTMatchers/ASTMatchers.h | ||
---|---|---|
3558 | I don't know enough objectie c to create a class, instantiate an object and point a pointer to it. But looking at the definition of the pointsToMatcher it also simply uses isAnyPointer(). So I'm wondering if we should only define isPointer() here but use isAnyPointerType() to be consistent with it. |
include/clang/ASTMatchers/ASTMatchers.h | ||
---|---|---|
3558 | Shouldn't we then not just define isAnyPointer? |
Sorry for the delay in review. Would be interesting to get an example that is different between isAnyPointerType and isPointerType.