Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
CodingGuidelines: style for multi-line comments
author
brian m. carlson
<sandals@crustytoothpaste.net>
Sat, 12 Oct 2013 00:45:46 +0000
(
00:45
+0000)
committer
Jonathan Nieder
<jrnieder@gmail.com>
Mon, 14 Oct 2013 19:48:06 +0000
(12:48 -0700)
The style for multi-line comments is often mentioned and should be documented
for clarity.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Documentation/CodingGuidelines
patch
|
blob
|
history
raw
|
patch
| inline |
side by side
(from parent 1:
110f415
)
diff --git
a/Documentation/CodingGuidelines
b/Documentation/CodingGuidelines
index e5ca3b75d3778308ee1b7b20e3a86475244f7b96..a600e35c810b74848062dee8d74e573192c09e2c 100644
(file)
--- a/
Documentation/CodingGuidelines
+++ b/
Documentation/CodingGuidelines
@@
-145,6
+145,14
@@
For C programs:
they were describing changes. Often splitting a function
into two makes the intention of the code much clearer.
+ - Multi-line comments include their delimiters on separate lines from
+ the text. E.g.
+
+ /*
+ * A very long
+ * multi-line comment.
+ */
+
- Double negation is often harder to understand than no negation
at all.