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
+1
-6
1 addition, 6 deletions
Coding-Guidelines.md
with
1 addition
and
6 deletions
Coding-Guidelines.md
View page @
45d72be9
...
...
@@ -53,7 +53,7 @@ This rule is aimed at improving the readability of the code.
These rules are mostly aimed at keeping the code readable and consistent.
-
**Functions generally should return an integer value which tells the caller if there were problems**
-
**No function should be longer than about 80 lines**
-
**No function should be longer than about 80 lines**
Split functions in multiple ones to improve readability of the code
## **Naming conventions**
...
...
@@ -81,9 +81,6 @@ enum EventIDs {
}
```
Best Practices
-------------------
### Logging
...
...
@@ -102,8 +99,6 @@ l'overload per altre classi... si può sempre creare un metodo toString() :P)
Ultimo pro, LOG_DEBUG(), LOG_INFO(), ... son piu' veloce da scrivere rispetto a
Logger::Logger::Antani
\<
Antani::lol::blabla
\>
().
### Debugging
Secondo me il modo migliore e fare una serie di macro in stile
...
...
This diff is collapsed.
Click to expand it.