Difference between revisions of "Talk:Coding style"
From Code::Blocks
m (More typo's) |
(CamelCase) |
||
| Line 10: | Line 10: | ||
Don't know if and how this can be done, but that would be very handy to have. | Don't know if and how this can be done, but that would be very handy to have. | ||
| + | |||
| + | == CamelCase == | ||
| + | |||
| + | From the article it seems [http://en.wikipedia.org/wiki/CamelCase CamelCase] should be used for all variable and function names. | ||
| + | |||
| + | Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters. | ||
Revision as of 19:51, 21 May 2007
How about comments?
Well I'm not an developer. It is pretty safe to say use "//" (C++ style) comments, and not the C style ones.
AStyle, should it be on ANSI?
As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?
As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.
Don't know if and how this can be done, but that would be very handy to have.
CamelCase
From the article it seems CamelCase should be used for all variable and function names.
Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.
