CODING_STYLE: Mention preferred comment form
Our defacto coding style strongly prefers /* */ style comments over the single-line // style, and checkpatch enforces this, but we don't actually document this. Mention it in CODING_STYLE. Suggested-by: Thomas Huth <thuth@redhat.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
This commit is contained in:
parent
a6e3707ece
commit
25ac5bbec4
@ -116,3 +116,10 @@ if (a == 1) {
|
|||||||
Rationale: Yoda conditions (as in 'if (1 == a)') are awkward to read.
|
Rationale: Yoda conditions (as in 'if (1 == a)') are awkward to read.
|
||||||
Besides, good compilers already warn users when '==' is mis-typed as '=',
|
Besides, good compilers already warn users when '==' is mis-typed as '=',
|
||||||
even when the constant is on the right.
|
even when the constant is on the right.
|
||||||
|
|
||||||
|
7. Comment style
|
||||||
|
|
||||||
|
We use traditional C-style /* */ comments and avoid // comments.
|
||||||
|
|
||||||
|
Rationale: The // form is valid in C99, so this is purely a matter of
|
||||||
|
consistency of style. The checkpatch script will warn you about this.
|
||||||
|
Loading…
Reference in New Issue
Block a user