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>
This commit is contained in:
parent
395726717b
commit
7df3f55b92
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user