From: Jamie Lokier <jamie@shareable.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] CODING_STYLE: {} as in linux kernel
Date: Wed, 7 Oct 2009 10:11:27 +0100 [thread overview]
Message-ID: <20091007091126.GB12384@shareable.org> (raw)
In-Reply-To: <20091006190115.GA4768@redhat.com>
Michael S. Tsirkin wrote:
> 4. Block structure
>
> -Every indented statement is braced; even if the block contains just one
> -statement. The opening brace is on the line that contains the control
> -flow statement that introduces the new block; the closing brace is on the
> -same line as the else keyword, or on a line by itself if there is no else
> -keyword. Example:
> +If an indented block contains just one statement, it is not braced. This
> +matches the Linux coding style. The opening brace of a block is on the line
> +that contains the control flow statement that introduces the new block; the
> +closing brace is on the same line as the else keyword, or on a line by itself
> +if there is no else keyword. Example:
>
> - if (a == 5) {
> + if (a == 5)
> printf("a was 5.\n");
> - } else if (a == 6) {
> + else if (a == 6) {
> printf("a was 6.\n");
> - } else {
> + printf("multiply by 7 to get the answer.\n");
> + } else
> printf("a was something else entirely.\n");
> - }
>
> An exception is the opening brace for a function; for reasons of tradition
> and clarity it comes on a line by itself:
> @@ -75,4 +75,5 @@ and clarity it comes on a line by itself:
>
> Rationale: a consistent (except for functions...) bracing style reduces
> ambiguity and avoids needless churn when lines are added or removed.
> +This matches the linux coding style.
Actually the above does not match the Linux coding style, and it's ugly too.
This is the Linux style:
Do not unnecessarily use braces where a single statement will do.
if (condition)
action();
This does not apply if one branch of a conditional statement
is a single statement. Use braces in both branches.
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
-- Jamie
next prev parent reply other threads:[~2009-10-07 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 19:01 [Qemu-devel] [PATCH] CODING_STYLE: {} as in linux kernel Michael S. Tsirkin
2009-10-06 21:08 ` Stefan Weil
2009-10-06 21:43 ` Anthony Liguori
2009-10-07 12:59 ` Markus Armbruster
2009-10-06 21:41 ` Stuart Brady
2009-10-07 9:11 ` Jamie Lokier [this message]
2009-10-07 14:12 ` Kevin Wolf
2009-10-07 14:54 ` Gerd Hoffmann
2009-10-07 17:09 ` Stuart Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091007091126.GB12384@shareable.org \
--to=jamie@shareable.org \
--cc=blauwirbel@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).