From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, blauwirbel@gmail.com
Subject: Re: [Qemu-devel] [PATCH] Document Qemu coding style
Date: Mon, 30 Mar 2009 13:02:12 -0600 (MDT) [thread overview]
Message-ID: <20090330.130212.1723234361.imp@bsdimp.com> (raw)
In-Reply-To: <f43fc5580903301128y2a8432f4u6b7d9375e29a5c82@mail.gmail.com>
In message: <f43fc5580903301128y2a8432f4u6b7d9375e29a5c82@mail.gmail.com>
Blue Swirl <blauwirbel@gmail.com> writes:
: > +An exception is the opening brace for a function; for reasons of tradition
: > +and clarity it comes on a line by itself:
: > +
: > + void a_function(void)
: > + {
: > + do_something();
: > + }
: > +
: > +Rationale: a consistent (except for functions...) bracing style reduces
: > +ambiguity and avoids needless churn when lines are added or removed.
: > +Furthermore, it is the Qemu coding style.
:
: No, this is the K&R style. Quoting linux/Documentation/CodingStyle:
:
: Heretic people all over the world have claimed that this inconsistency
: is ... well ... inconsistent, but all right-thinking people know that
: (a) K&R are _right_ and (b) K&R are right. Besides, functions are
: special anyway (you can't nest them in C).
And besides, there's lots of almost-smart tools that operate on source
code that know this is always true... Or at least historically that's
been the case, don't know of any widely used ones today, but I doubt
they were all fixed...
Warner
next prev parent reply other threads:[~2009-03-30 19:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 21:23 [Qemu-devel] [PATCH] Document Qemu coding style Avi Kivity
2009-03-30 1:15 ` malc
2009-03-30 18:28 ` Blue Swirl
2009-03-30 19:02 ` M. Warner Losh [this message]
2009-03-30 19:55 ` Avi Kivity
2009-03-30 19:54 ` Avi Kivity
2009-03-30 21:43 ` Lennart Sorensen
2009-03-30 22:15 ` M. Warner Losh
2009-03-30 23:38 ` Lennart Sorensen
2009-03-31 0:09 ` M. Warner Losh
2009-03-31 5:59 ` Laurent Desnogues
2009-03-31 12:58 ` David Turner
2009-03-31 13:31 ` Avi Kivity
2009-03-31 21:18 ` David Turner
2009-03-31 16:18 ` Blue Swirl
2009-03-31 21:48 ` David Turner
2009-03-31 22:38 ` malc
2009-03-31 23:28 ` David Turner
2009-03-31 23:49 ` malc
2009-04-01 0:25 ` David Turner
2009-04-01 1:02 ` malc
2009-04-01 9:04 ` Daniel P. Berrange
2009-03-30 19:58 ` Avi Kivity
2009-03-30 20:10 ` Glauber Costa
2009-03-30 20:35 ` Avi Kivity
2009-03-30 20:37 ` Glauber Costa
2009-03-30 20:20 ` Andreas Färber
2009-03-30 21:45 ` Lennart Sorensen
2009-03-30 22:16 ` M. Warner Losh
2009-03-31 5:42 ` Gleb Natapov
2009-03-31 13:47 ` Paul Brook
2009-04-01 8:51 ` Richard W.M. Jones
2009-04-01 9:04 ` Avi Kivity
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=20090330.130212.1723234361.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=blauwirbel@gmail.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).