summaryrefslogtreecommitdiff
path: root/Documentation/CodingGuidelines
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2014-02-28 01:17:25 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-02-28 12:53:50 -0800
commitf57b6cfdf7b395adc6b3c813109c2eb53e93809a (patch)
treeaa23a72e18f2bbee611a8c1f621c8c7740fb2bd0 /Documentation/CodingGuidelines
parentGit 1.8.5.5 (diff)
downloadtgif-f57b6cfdf7b395adc6b3c813109c2eb53e93809a.tar.xz
CodingGuidelines: mention C whitespace rules
We are fairly consistent about these, so most are covered by "follow existing style", but it doesn't hurt to be explicit. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/CodingGuidelines')
-rw-r--r--Documentation/CodingGuidelines11
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index ef67b53f72..ed432a80ca 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -126,6 +126,17 @@ For C programs:
"char * string". This makes it easier to understand code
like "char *string, c;".
+ - Use whitespace around operators and keywords, but not inside
+ parentheses and not around functions. So:
+
+ while (condition)
+ func(bar + 1);
+
+ and not:
+
+ while( condition )
+ func (bar+1);
+
- We avoid using braces unnecessarily. I.e.
if (bla) {