-
Notifications
You must be signed in to change notification settings - Fork 32
Coding Guidelines
Jeff Henning edited this page Oct 12, 2025
·
2 revisions
- 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, needed to compile CoolProp for older versions of Python. This means, in general, that the C++11 language standard should be used in the IF97 header file as it is the latest standard supported by CoolProp.