On Oct 22, 2013, at 10:27 PM, Clifford Yapp wrote: > This has considerable appeal - what technical approach did you have in mind?
Basically just running a lintian program (probably astyle) during non-release compilation. If it doesn't pass, report and halt the build. Most likely easiestly hooked into BRLCAD_ADDLIB() and friends. >> To that same end, I think it's time to eliminate this common source of >> discussion too. Unless there's an objection, I propose and plan to update >> all sources to only use spaces for indentation. > > Sounds good - I would suggest at the same time we do this we also > publicize the correct setting updates for Emacs and vim. I think this is pretty much requisite for the task along with numerous doc updates (in our code, docs, on wiki, elsewhere), extensive testing, and care so that we don't have multiple commit passes polluting the history. Cheers! Sean ------------------------------------------------------------------------------ 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
