for_developers:style_guide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
for_developers:style_guide [2016/02/12 09:32] – abajric | for_developers:style_guide [2019/01/22 17:06] – update broken link. kunz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Coding Style Guide ====== | ====== Coding Style Guide ====== | ||
- | EEROS is written primarily in C++, and its developers follow the [[https:// | + | EEROS is written primarily in C++, and its developers follow the [[https:// |
=== #define Guards === | === #define Guards === | ||
Line 24: | Line 24: | ||
=== File Names and Extensions === | === File Names and Extensions === | ||
- | + | * File names | |
- | File names: | + | |
- | + | | |
- | File names should be the same as the class name. For example, for the class ExampleClass the header file is ExampleClass.hpp and the source file ExampleClass.cpp | + | |
- | + | | |
- | If there is more then one class defined in a single file, we use the module name for the file name. A module name always starts with a small letter (e.g. exampleModule.cpp) | + | |
- | + | ||
- | File extensions: | + | |
- | + | ||
- | C++ Source Code: use .cpp | + | |
- | C++ Headerfiles: | + | |
=== Variable Names === | === Variable Names === |
for_developers/style_guide.txt · Last modified: 2021/06/09 18:31 by ursgraf