6 |
to fixes or questions might often come late. Hopefully the bug and patch tracking |
to fixes or questions might often come late. Hopefully the bug and patch tracking |
7 |
features of Savannah help us not lose users' input. |
features of Savannah help us not lose users' input. |
8 |
|
|
|
|
|
9 |
Source code style: |
Source code style: |
10 |
|
|
11 |
- end debug messages with a newline (\n) |
- indentation is two spaces per level, no tabs. |
12 |
|
- end debug messages with a trailing newline (\n). |
13 |
- no space between function and opening bracket. |
- no space between function and opening bracket. |
14 |
- one space between keyword and opening bracket. |
- one space between keyword and opening bracket. |
15 |
- one space and no newline before opening curly braces. |
- one space and no newline before opening curly braces. |
16 |
|
- spaces surrounding assignment and comparisons. |
17 |
|
- use current source code style as further reference. |
18 |
|
|
19 |
|
Source code self documentation style: |
20 |
|
|
21 |
|
- JavaDoc compliant and Doxygen compatible. |
22 |
|
- Function documentation above functions in .c files, not .h files. |
23 |
|
- Use current documentation style as further reference. |
24 |
|
|
25 |
Bug reports and patches: |
Bug reports and patches: |
26 |
|
|
27 |
- Make sure you are reporting bugs or send patches against the latest sources.That usually means code in CVS |
- Make sure you are reporting bugs or send patches against the latest sources.That usually means code in CVS |