Difference between revisions of "RidgeRun Developer Manual/Coding Styles/C++"
Line 5: | Line 5: | ||
== Introduction to 'C++' Coding Styles == | == Introduction to 'C++' Coding Styles == | ||
− | + | When writing software source code there are many coding styles as the concept covers a lot of aspects (some of them subjective). In general RidgeRun tries to follow the [https://google.github.io/styleguide/cppguide.html Google C++ Style Guide]. | |
== Other good practices == | == Other good practices == |
Revision as of 17:36, 21 October 2020
WORK IN PROGRESS. Please Contact RidgeRun OR email to support@ridgerun.com if you have any questions. |
RidgeRun Developer Manual |
---|
![]() |
Coding Styles |
Development Tools |
Editors |
Debugging Tools |
Methodologies |
Design Patterns |
Testing |
Build Systems |
Contact Us |
Introduction to 'C++' Coding Styles
When writing software source code there are many coding styles as the concept covers a lot of aspects (some of them subjective). In general RidgeRun tries to follow the Google C++ Style Guide.
Other good practices
Conditionals
- Keep the constants at the left side of a comparison. This applies to all C++ comparison operators. For example:
if ( NULL == var ) {
// ...
}
This is to avoid possible bugs like:
if ( var = NULL ) {
// ...
}
A derived good practice is to use const
keyword as much as you can:
const int val = 1;
if (val = 2) { // This should not compile
...
}