From: Markus Armbruster <armbru@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] CODING_STYLE: {} as in linux kernel
Date: Wed, 07 Oct 2009 14:59:58 +0200 [thread overview]
Message-ID: <87ws37z7e9.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <4ACBBA0E.7040905@codemonkey.ws> (Anthony Liguori's message of "Tue\, 06 Oct 2009 16\:43\:42 -0500")
Anthony Liguori <anthony@codemonkey.ws> writes:
> Stefan Weil wrote:
>> Michael S. Tsirkin schrieb:
>>
>>> Most people seem to hate using {} around sngle-statement blocks.
>>> And code isn't consistent either way. So let's change our standard
>>> to something most people like, and eliminate the pain source.
>>>
>>>
>>
>> Inconsistency is not an argument for or against {}.
>> I don't like single statement blocks without {}
>> because of my personal experience with all kinds
>> of code standard variants.
>>
>> Please don't change the qemu standard, I like it as it is.
>>
>
> I've never liked this but I would rather not see unnecessary churn so
> I'd prefer to keep the coding style as-is.
The existing code uses both brace styles. We didn't convert it
wholesale when the "thou shalt use braces" rule was written into the
coding style, because we didn't want the churn. We can handle it just
the same now. Churn is not an argument then.
I dislike redundant braces, and support the change Michael proposed.
next prev parent reply other threads:[~2009-10-07 13:00 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 [this message]
2009-10-06 21:41 ` Stuart Brady
2009-10-07 9:11 ` Jamie Lokier
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=87ws37z7e9.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.