Talk:Coding style: Difference between revisions
From Code::Blocks
AStyle, should it be on ANSI? |
m Fixed a stupid typo |
||
| Line 5: | Line 5: | ||
== AStyle, should it be on ANSI? == | == AStyle, should it be on ANSI? == | ||
As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B | 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. | 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 how if and how this can be done, but that would be very handy to have. | Don't know how if and how this can be done, but that would be very handy to have. | ||
Revision as of 19:41, 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 how if and how this can be done, but that would be very handy to have.
