[cfe-dev] Checker Plugins

[Jordy Rose]

The idea's come up before, right? I feel like having pluggable check-ins is one of the goals of the analyzer, even as everything is refactored over and over. It would be convenient for organizations to make their own API checks, like we do for Unix and Cocoa (a little). Right? Attributes only go so far.

Anyway, I hacked up a quick plug-in system over the last few days. It approximates Argyrios' very nice group/package system with a poor text-matching version of the registration system, and supports multiple new checkers in one loadable library. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CheckerPlugins.2.patch
Type: application/octet-stream
Size: 15781 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20110604/8216d20a/attachment.obj>
-------------- next part --------------


I'm not suggesting that this is code that should go into trunk now, or even that this is the right approach to checker plug-ins, but I wanted to bring it up again, to see if there's any way to make progress on it.

(At the very least we'd want some kind of "checker API version" token, so that when we make massive refactorings, we can invalidate old plug-ins.)

Comments?
Jordy

P.S. Why is the static analyzer "ento"? *grin*