Programming Naming Conventions : Différence entre versions
De Transport
(Page créée avec « I tend to favour the following rules, as can be seen in the Traffic Intelligence project * UpperCamelCase for classes * … ») |
|||
| Ligne 1 : | Ligne 1 : | ||
| − | I tend to favour the following rules, as can be seen in the | + | I tend to favour the following rules, as can be seen in the [https://bitbucket.org/Nicolas/trafficintelligence Traffic Intelligence project] |
* UpperCamelCase for classes | * UpperCamelCase for classes | ||
* lowerCamelCase for methods | * lowerCamelCase for methods | ||
| Ligne 9 : | Ligne 9 : | ||
Other resources | Other resources | ||
| − | * | + | * [http://en.wikipedia.org/wiki/Naming_convention_(programming) Wikipedia] |
Version du 12 août 2012 à 18:12
I tend to favour the following rules, as can be seen in the Traffic Intelligence project
- UpperCamelCase for classes
- lowerCamelCase for methods
- all upper cases for constants
- explicit names, even if they have to be long, for variables
- 4 spaces for indentation in Python code (no tab!)
- shared pointers in C++
- const and references for function arguments wherever possible in C++
Other resources
