Reference Code Standard
Follow Google’s guidelines which includes coding conventions and naming style:
Exceptions to the Standard
None. Exceptions that would benefit a specific project should be documented along with a rationale for the exception.
Implementing the Standard
Tools/Procedures | Type | Notes |
---|---|---|
cpplint | Open Source | Validates Google code style. It can be modified to account for any exceptions we add to the original standard. |
Visual Studio 2022 | Commercial | IntelliSense Code Linter for C++ evaluates as you type |
ReSharper C++ | Commercial | IntelliSense Code Linter for C++ evaluates as you type |
clang-format | Free | Formats source code according to style guide. |
Recommended Reading
-
Boost Library Req and Guidelines
- Good documentation of what goes into setting up a Boost library project. Contains links to other documents and references to books.
Was this page helpful?
Thanks for your feedback!