^ —————. —.— . . —.— . . .————— . .
——— | | | | | | || | | | |
—(o)— | | | | | | | | | |———— '————|
——————— | | | | | | | || | |
————————— —————' —'— ' —'— ' ' '————— '
home manual roadmap issues status papers download
- Timestamp:
-
02/04/2019 10:58:39 PM (6 years ago)
- Author:
-
mornfall
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
initial
|
v1
|
|
| 11 | 11 | - line breaks in if/while/... should be after logical operators if possible |
| 12 | 12 | - multi-line function calls or expressions should indent to align with the same paren nesting level |
| | 13 | - lines should be wrapped after 100 columns (106 at most) |
| | 14 | - member variables should start with an underscore (unless they are meant for public access) but remain public |
| | 15 | - filenames should end in .hpp, .tpp and .cpp for C++ code, .c and .h for C |
| | 16 | - template functions and methods can be implemented in header files or .tpp files |
| | 17 | - prefer good function/variable names to comments, but comment non-obvious code |
| | 18 | |
| | 19 | Commit Logs |
| | 20 | - should start with a tag, followed by a colon, a space, and a single sentence |
| | 21 | - common tags: dios, lart, VM, MC, libc, rst, ... (check darcs log -i file/you/modified) |
| | 22 | - the sentence starts with a capital letter and ends with a period |
| | 23 | - extended messages should only be used sparingly (and separated from the summary by an empty line) |
| | 24 | - the total length limit is 80 characters |
| | 25 | - be concise, grammatically correct and use a spellchecker (or otherwise avoid typos) |
| | 26 | - if you can't come up with a name, try splitting the patch |