rewrite the style guide

This commit is contained in:
2025-08-12 12:38:34 +02:00
parent c4612010f8
commit a64bd33973

View File

@@ -24,9 +24,10 @@ Within [intdef.h](/src/util/intdef.h) there live definitions for static-width in
### style guide ### style guide
- Code must be written correctly, read [Correct C](./correct-c.md) if more information is required. - Code must be written correctly, read [Correct C](./correct-c.md) if more information is required.
- K&R style braces/[indentation](https://en.wikipedia.org/wiki/Indentation_style) - `snake_casing` is used, with no [Hungarian notation](https://en.m.wikipedia.org/wiki/Hungarian_notation). (macros are all-uppercase, with a few exceptions)
- typedefs are discouraged - [K&R style braces/indentation](https://en.wikipedia.org/wiki/Indentation_style) should be used.
- snake_case is used for all user-defined symbols. Macros are often all-uppercase, same goes for enums and other types of compile-time constants. - For indentation tabs are used, and are assumed to be 8 spaces wide. For alignment spaces should be used.
- tabs are used for indentation, spaces are used for alignment. - A space should precede a pointer `*` should be with the name, rather than the type. For `const` clarity, and chains such as: `u8 *a, *b, *c;`
- British spelling is (generally) preferred, but not enforced. - Generally speaking, British spelling is preferred. Define potential macros for, or when using alternate dialects.
- commits should attempt to convey clearly what is being changed, for the sanity of the maintainer(s). - Grammar should be correct. (`don't` or `do not`, not `dont`)
- Commits should attempt to convey clearly what is being changed, for the sanity of the maintainer(s).