qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] CODING_STYLE: don't allow non-indented statements after if/else blocks
Date: Mon, 26 Oct 2009 18:02:52 +0200	[thread overview]
Message-ID: <f43fc5580910260902l3b2c255cgd78d67fadd88890c@mail.gmail.com> (raw)
In-Reply-To: <20091026062637.GA21562@volta.aurel32.net>

On Mon, Oct 26, 2009 at 8:26 AM, Aurelien Jarno <aurelien@aurel32.net> wrote:
> Rationale: The following code is difficult to read, but allowed by the
> current coding style.

Fully agree.

> +Every control flow statement is followed by a new indented and braced
> +block; 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:

I think an exception should be granted for "else if" case, otherwise
the style would require braces around "if", like:
    if (a == 5) {
        printf("a was 5.\n");
    } else {
        if (a == 6) {
            printf("a was 6.\n");
        }
    } else {
        printf("a was something else entirely.\n");
    }

Picking nits: "while" is a control flow statement, even in "do {}
while" statement and then it would illegal to require a braced block
after the "while" statement.

  reply	other threads:[~2009-10-26 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  6:26 [Qemu-devel] [PATCH] CODING_STYLE: don't allow non-indented statements after if/else blocks Aurelien Jarno
2009-10-26 16:02 ` Blue Swirl [this message]
2009-10-26 20:03   ` Aurelien Jarno
2009-10-26 20:20     ` Blue Swirl
2009-10-26 20:27       ` Aurelien Jarno
2009-10-26 21:16         ` Anthony Liguori

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=f43fc5580910260902l3b2c255cgd78d67fadd88890c@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=aurelien@aurel32.net \
    --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).