On Tue, Oct 22, 2013 at 10:27 PM, Clifford Yapp <[email protected]> wrote: > On Tue, Oct 22, 2013 at 9:06 PM, Christopher Sean Morrison > <[email protected]> wrote: >> >> I propose in advance of GCI that we establish style enforcement as part of >> the build so that we don't have to personally discuss / explain style >> issues. Basically, we'd integrate a style check that would run during >> compilation. If a file fails our style check, it results in a compilation >> error. > > This has considerable appeal - what technical approach did you have in mind?
For what it's worth, we might be able to start with something like OpenBSD's indent and customize it to just do checks for our particular style points instead of actually reformatting, then wire it in to the build system using a trick similar to the one I use for the xml DocBook validation. That would allow for compiler/platform independent verification, unless there's already a better approach out there: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/indent/ Cheers, CY ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
