[cfe-dev] analysis vs fixit

Axel Naumann Axel.Naumann at cern.ch
Sat Jan 23 12:34:18 PST 2010


I have written a tiny coding convention checker, see attachment. You're
very welcome to include it (after a long period of tough reviews :-).
It's really only a proof-of-concept for now, missing basic things like
validation ("do we have a config file?"), customization, and: fixit. And
because I'm still a novice to clang I'm sure that it's a) suboptimal and
b) wrong :-) I will definitely benefit from your comments.

The fixit problem is that the convention checker (also according to
Mike, see
should be seen as an analysis. But if the frontend does analysis I don't
see how it can do fixit :-( Any suggestions? Shouldn't -fixit and
-analyze be both allowed at the same time? Or am I misunderstanding some
basic concept here?

Cheers, Axel.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: CodingConvention.tar.bz2
Type: application/x-bzip
Size: 8082 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20100123/42c25fd8/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: coderules.txt
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20100123/42c25fd8/attachment.txt>

More information about the cfe-dev mailing list