| Message ID | e3baf012344df07a464dba997e8e32f521c8c195.1722323818.git.ps@pks.im (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 7df3f55b92ef39239b7b84fee6b89a87a304a58f |
| Headers | show |
| Series | Documentation: some coding guideline updates | expand |
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 1d92b2da03..65fba3b810 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -214,6 +214,16 @@ For C programs: - We use tabs to indent, and interpret tabs as taking up to 8 spaces. + - Nested C preprocessor directives are indented after the hash by one + space per nesting level. + + #if FOO + # include <foo.h> + # if BAR + # include <bar.h> + # endif + #endif + - We try to keep to at most 80 characters per line. - As a Git developer we assume you have a reasonably modern compiler
In the preceding commit, we have settled on using a single space per nesting level to indent preprocessor directives. Clarify our coding guidelines accordingly. Signed-off-by: Patrick Steinhardt <ps@pks.im> --- Documentation/CodingGuidelines | 10 ++++++++++ 1 file changed, 10 insertions(+)