Date: Thu, 25 Aug 2011 10:37:37 -0700
From: Douglas Gregor <dgregor@apple.com>
Subject: Re: [cfe-dev] null pointer literals, warnings, and fixups
To: Jeffrey Yasskin <jyasskin@google.com>
Cc: cfe-dev Developers <cfe-dev@cs.uiuc.edu>
Message-ID: <E190210B-61B4-4ECD-A2C1-1839A1445803@apple.com>
Content-Type: text/plain; CHARSET=US-ASCIII don’t think these warnings would be suitable for Clang. Such
style-checking transformations belong in a separate tool (e.g., like the ARC
migrator).Do you guys run the ARC migrator on every build?
No. It’s a standalone tool that will be run once for a code base.
I’m curious if
there’s an open source example of how to set up a style checker you
run on every build that’s not part of core clang.I don’t know of any.
- Doug
I’ve heard good things about Artistic Style (http://astyle.sourceforge.net), however I have some doubt regarding its full C++ support given the highly complicated syntax. It is limited to indentation though, and does not handle, I think, naming conventions for example.
– Matthieu