> 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.
I would like to have a CMake variable to switch it off. I'm afraid
MSVC needs another day to compile with this check because of slow file
operations.
> 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. This will preserve our
> current appearance and indent level. This is the more portable and
> patch-friendly option as well. It coincidentally matches the Apache style
> guide, though that is just an observation, not a consideration.
+2 :)
Regards,
Daniel
------------------------------------------------------------------------------
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
