guidelines

C++ Programming Guidelines

We base our style and best practice guidelines on the ones at geosoft.no with a few modifications.

• Syle guidelines
• Best practice

Style guideline additions:

11. Don't use the underscore _ suffix for private members.
12. We use the Id suffix instead of the No suffix.
13. We use the file extensions .cpp and .hpp.
14. In some cases it might be permitted to define methods in the header files (e.g. when templating)
15. break and continue are permitted.
16. Use nullptr for Null-Pointers instead of 0 or NULL
17. For the else block, either put opening and closing bracket on the same line or both on separate lines.

        // DO:
        if ( ) {
          // do something
        } else {
          // do something else
        }