documentation:coding_practices
Releases
Current version
Git/Latestdiff: 1.5.6
Latest Snapshots
Produced after each commit or rebase to new upstream version
GIT
RSBAC source code, can be unstable sometimes
Events
No events planned
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
documentation:coding_practices [2005/11/22 13:12] kang spelling |
documentation:coding_practices [2006/05/02 15:40] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| General kernel rules are, no more than 10 variables per function, no more than 2 or 3 console screens of text per function (except switch..case), no more than 3 levels of indentation. | General kernel rules are, no more than 10 variables per function, no more than 2 or 3 console screens of text per function (except switch..case), no more than 3 levels of indentation. | ||
| - | Of course this may not always be applicable, but when you reach any of thoses values you can start checking if there is not something you could have made simpler :) | + | Of course this may not always be applicable, but when you reach any of those values you can start checking if there is not something you could have made simpler :) |
| ===== Indent ===== | ===== Indent ===== | ||
| Line 47: | Line 47: | ||
| If your code is full of endif}}}}}}} then it should be rewritten :) | If your code is full of endif}}}}}}} then it should be rewritten :) | ||
| Ok, sarcasms apart, in most case its easy to see or to push "%" (or equivalent in non-vim editors) to see where the ifdef is from. For functions, your editor should tell you in which function you are and in which sub-bracket you are. | Ok, sarcasms apart, in most case its easy to see or to push "%" (or equivalent in non-vim editors) to see where the ifdef is from. For functions, your editor should tell you in which function you are and in which sub-bracket you are. | ||
| - | Please dont use thoses too much. | + | Please dont use them too much. |
| * Do not comment without reason. Why commenting when there is NO need to ? | * Do not comment without reason. Why commenting when there is NO need to ? | ||
documentation/coding_practices.1132661557.txt.gz · Last modified: 2006/05/02 15:40 (external edit)