Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Skyward Boardcore
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Avionics
Software Development
Skyward Boardcore
Wiki
Coding Guidelines
Changes
Page history
New page
Templates
Clone repository
Updated Coding Guidelines (markdown)
authored
7 years ago
by
Luca Erbetta
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Coding-Guidelines.md
+2
-0
2 additions, 0 deletions
Coding-Guidelines.md
with
2 additions
and
0 deletions
Coding-Guidelines.md
View page @
cd08946e
...
...
@@ -53,6 +53,8 @@ Enum classes restrict the scope of their members and are strongly-typed.
-
**The return value of non-void functions must be checked by each calling**
This is done to check if the function had an error.
-
**Use C++ style cast (static_cast, dynamic_cast…) instead of their C counterparts**
-
**Initialize objects in their costructors: avoid init() functions when possible**
It's very easy to forget to call an object's init() method, leaving objects in a undefined state.
## **Commenting rules**
-
**Every function shall be preceded by a doxygen-style comment describing the purpose of the function, its parameters and the return value.**
...
...
This diff is collapsed.
Click to expand it.