On 06/22/2015 03:36 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> Directions where I can find a complete set of rules how the
> code should be formatted would also suffice.
We don't have it formally documented anywhere. Basics:
* 79 columns or less (only one that is enforced with a test)
* indent with 2 spaces, no tabs
* opening '{' gets its own line and aligns with inner code
* CamelCase names for class members
* this->Member for references to class members
Generally just try to match style of surrounding code.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
