-
Notifications
You must be signed in to change notification settings - Fork 31
Coding Guidelines
Jeff Henning edited this page Mar 17, 2018
·
1 revision
- Please use spaces for indentation rather than tabs. This creates a consistent look in whatever editor the other developers are using and makes for cleaner presentation.
- Please follow the Google C++ Style Guide for consistent coding philosophy and structure.
- Please try to write DRY code.
- One of the goals of CoolProp is to maintain backward compatibility with older compilers, including Microsoft Visual C++ 2008, which is still needed to compile for Python 2.7. This means, in general, that newer C++11 language standards should not be used as they are not supported by MSVC08. The repository Travis-CI scan should automatically identify any language constructs that are not supported when code is submitted to the project.