design:coding_style_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| design:coding_style_guide [2025/05/04 16:48] – [Global identifiers] asie | design:coding_style_guide [2025/05/05 15:17] (current) – [Commenting] asie | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| * For example, '' | * For example, '' | ||
| * Some macros can refer to a type; for readability and to distinguish it from function categories, these should be // | * Some macros can refer to a type; for readability and to distinguish it from function categories, these should be // | ||
| - | * For example, an I/O port will be referred to as '' | + | * For example, an I/O port will be referred to as '' |
| - | ===== Code formatting | + | ===== Code style ===== |
| + | |||
| + | * Braces are always on the same line, and are separated with a space. | ||
| + | * If it doesn' | ||
| <code c> | <code c> | ||
| Line 38: | Line 41: | ||
| if (multi_line) { | if (multi_line) { | ||
| braces_on_the_same_line(1); | braces_on_the_same_line(1); | ||
| - | | + | |
| - | // ... but treat sizeof, etc. like a function. | + | |
| - | memcpy(&b, &a, sizeof(a)); | + | |
| } | } | ||
| } | } | ||
| </ | </ | ||
| - | ===== Commenting | + | * Pointers are declared with the asterisk '' |
| + | |||
| + | <code c> | ||
| + | const void __far *return_pointer(void __far *my_pointer); | ||
| + | </ | ||
| + | |||
| + | ===== Documentation | ||
| Use [[https:// | Use [[https:// | ||
| Line 51: | Line 58: | ||
| * Javadoc-style '' | * Javadoc-style '' | ||
| * For one-line comments, such as on enumerated types, '' | * For one-line comments, such as on enumerated types, '' | ||
| + | * When writing internal header macros/ | ||
| ===== Best practices ===== | ===== Best practices ===== | ||
design/coding_style_guide.1746377326.txt.gz · Last modified: by asie
