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
Update Coding Guidelines
authored
6 years ago
by
Luca Erbetta
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Coding-Guidelines.md
+1
-1
1 addition, 1 deletion
Coding-Guidelines.md
with
1 addition
and
1 deletion
Coding-Guidelines.md
View page @
efc07d99
...
...
@@ -75,7 +75,7 @@ Split functions in multiple ones to improve readability of the code
Example:
`float readTemperatureSample()`
Exception: Acronyms in function names will be UPPERCASE. Example:
`bool selfTestIMU()`
-
**Classes, structs and enums will be named using CamelCaseNotation**
Example:
`class TemperatureSensor
{};`
Example:
`class TemperatureSensor
{...}`
Exception: As for functions, acronyms in class names will be UPPERCASE. Example:
`class FSM {...}`
-
**Constants and enum members will be named using ALL_CAPS_WITH_UNDERSCORES**
Example 1:
`float TEMPERATURE_SAMPLE;`
...
...
This diff is collapsed.
Click to expand it.