Coding Guidelines

Please use 4 spaces for indentation rather than tabs. This creates a consistent look in whatever editor the other developers are using and makes for cleaner presentation, since many editors and GitHub set their tab widths differently.
When modifying C++ code, please use clang-format to format your C++ files using the repository's formatting rules in .clang-format and .clang-tidy. The clang-format tool is integrated into almost every editor and IDE available today (Vim, Emacs, Visual Studio, VS Code, CLion, et. al.) and is very easy to run from those environments. All pull requests will be run through clang-format as part of the Continuous Integration (CI) tests and will indicate any C++ file formatting issues. This keeps all of the repository code consistent to a specific style.
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, C++17 language standards should be used. The repository Travis-CI scan should automatically identify any language constructs that are not supported when code is submitted to the project.

Navigation Menu