diff options
| author | Enrico Granata <egranata@apple.com> | 2014-09-19 18:21:05 +0000 |
|---|---|---|
| committer | Enrico Granata <egranata@apple.com> | 2014-09-19 18:21:05 +0000 |
| commit | 47caf9a95618142a03316f91a72eed1910a79b14 (patch) | |
| tree | b6268e1cc325cd52932f921b50b2a2df9ca0036a /llvm/tools/llvm-cov/CodeCoverage.cpp | |
| parent | 4505f3a73db80414c9fed0049b8a75b6c4d1b1d8 (diff) | |
| download | llvm-47caf9a95618142a03316f91a72eed1910a79b14.zip llvm-47caf9a95618142a03316f91a72eed1910a79b14.tar.gz llvm-47caf9a95618142a03316f91a72eed1910a79b14.tar.bz2 | |
Extend the member function discovery APIs to also support Objective-C as well as C++
For the Objective-C case, we do not have a "function type" notion, so we actually end up wrapping the clang ObjCMethodDecl in the Impl object, and ask function-y questions of it
In general, you can always ask for return type, number of arguments, and type of each argument using the TypeMemberFunction layer - but in the C++ case, you can also acquire a Type object for the function itself, which instead you can't do in the Objective-C case
llvm-svn: 218132
Diffstat (limited to 'llvm/tools/llvm-cov/CodeCoverage.cpp')
0 files changed, 0 insertions, 0 deletions