On Wed, Jan 29, 2014 at 9:32 AM, Gregory Szorc <g...@mozilla.com> wrote: > On 1/28/14, 7:15 PM, Anthony Jones wrote: >> >> On 28/01/14 13:08, Nicholas Nethercote wrote: >>>> >>>> In the meantime, we should wrap up the pending discussions about other >>>> changes to the style guide, such as 80/100/infinite columns, >>>> member/parameter/local naming convention, and other threads that Gavin >>>> was >>>> going to start and one I'm going to start now ;-) >>> >>> >>> It's been a couple of weeks now. Can we move forward? >> >> >> A style verifier would be nice. > > > Building a style verifier for C++ is hard. You inevitably have to build it > on top of an existing parser (like Clang) or cobble something hacky together > [1], at which point you are chasing the language evolution and all kinds of > one-offs. > > I think it would be much easier to have the verifier be a derivative of the > formatting tool. Ideally the formatter would emit reasons/policies why it is > changing something. In read-only mode, it would behave as a verifier. The > Clang project might be receptive to this enhancement if it were proposed to > them. > > [1] http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform
Whatever tool we end up using needs to work on Windows. - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
