From: Patrick Steinhardt Date: Tue, 30 Jul 2024 07:24:38 +0000 (+0200) Subject: Documentation: clarify indentation style for C preprocessor directives X-Git-Tag: v2.47.0-rc0~157^2~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7df3f55b92ef39239b7b84fee6b89a87a304a58f;p=thirdparty%2Fgit.git Documentation: clarify indentation style for C preprocessor directives 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 Signed-off-by: Junio C Hamano --- 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 + # if BAR + # include + # 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