[cfe-commits] r122492 - in /cfe/trunk: include/clang/Analysis/DomainSpecific/ include/clang/GR/ include/clang/GR/BugReporter/ include/clang/GR/Checkers/ include/clang/GR/PathSensitive/ lib/Analysis/ lib/FrontendTool/ lib/GR/ lib/GR/Checkers/

Ted Kremenek kremenek at apple.com
Thu Dec 23 09:10:11 PST 2010

On Dec 23, 2010, at 8:52 AM, Chris Lattner wrote:

> On Dec 23, 2010, at 8:48 AM, Chris Lattner wrote:
>>>>> URL: http://llvm.org/viewvc/llvm-project?rev=122492&view=rev
>>>>> Log:
>>>>> Rename static analyzer namespace 'GR' to 'ento'.
>>>> Ok, I'll bite.  Ento?  "Inside; within"?
>>>> -Chris
>>> It's a suggestion from way back:
>> While perhaps cute, I think that lib/Checker is far more useful and obvious to people new to the codebase.
> To be clear, I care more about the source organization that the name of the "project".
> -Chris

The problem with libChecker is that we wanted to divide the "checkers" for the analyzer core.  We thus made them two libraries.  If we stayed with libChecker, we would have something like libChecker and libCheckers.  We used 'GR' (taking the prefix from most of the classes), but you argued that wasn't clear either.  I'm not terribly excited about using 'SA' since I don't want to send the message that this is the exclusive static analyzer that could be built on Clang, and indeed it only reflects a particular kind of approach.  It's very conceivable we could introduce other analysis engines over time.  How would they be labeled/organized?  Would they be separate llvm projects, like klee?

More information about the cfe-commits mailing list