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 <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Patrick Steinhardt committed
Jul 30, 2024 at 09:24 UTC
7df3f55b92ef39239b7b84fee6b89a87a304a58f
1 file changed
+10
Documentation/CodingGuidelines
+10
@@ -214,6 +214,16 @@ For C programs:
214
- We use tabs to indent, and interpret tabs as taking up to
215
8 spaces.
216
217
+ - Nested C preprocessor directives are indented after the hash by one
218
+ space per nesting level.
219
+
220
+ #if FOO
221
+ # include <foo.h>
222
+ # if BAR
223
+ # include <bar.h>
224
+ # endif
225
+ #endif
226
+
227
- We try to keep to at most 80 characters per line.
228
229
- As a Git developer we assume you have a reasonably modern compiler