[cfe-dev] Building upon the clang static analyzer

[Gábor Kozár]

Hi,

We're working on a static analysis tool that would enforce certain design
(coding) rules in some private C++ projects. So far we've been working on a
custom tool, using clang libtooling, to implement some fairly trivial
checks using AST matchers - however, we realized that building upon the
clang static analyzer would be a much better choice, especially when
implementing more complicated checks.

I have had a quick look at the static analyzer source code, and it appears
to me that it's basically an ASTFrontendAction
(lib/StaticAnalyzer/FrontendActions.h), which to me indicates that this is
"just another" tool built upon clang libtooling. Is this correct?
It would be extremely convenient for us if it were so, because we could
extend it seamlessly with our custom checkers into a custom analyzer tool.

I also read on the website of the static analyzer that C++ support is not
complete. However, I'm not sure how up-to-date the information on that
website is kept, so I'll just ask it here: what is the state of the C++
(and C++11) support?

Thanks!

(Btw, we are very impressed by clang, and its static analyzer. Thank you
for all your hard work! You guys are amazing!)

Gabor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130406/bc541823/attachment.html>