qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Turner <digit@google.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Document Qemu coding style
Date: Tue, 31 Mar 2009 14:58:50 +0200	[thread overview]
Message-ID: <60cad3f0903310558j554d6906q6f1244fd8a7449aa@mail.gmail.com> (raw)
In-Reply-To: <761ea48b0903302259p31b13c76s4c44396b8e33166b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

Very frankly, I don't think that a coding style, even strictly applied, is
going to make the QEMU code
easier to understand.

The real barriers to understanding are the lack of structure in the code,
liberal use of global macros
scattered randomly in the source code, exceedingly liberally named
functions, and sometimes obscure
implementation of simple concepts (*cough* CharDriverState), cramming
totally unrelated stuff in single
largish source files (vl.c for the win !), and a blatant lack of
documentation comments for a lot of subtle
stuff in there to explain the magic.

Braces and indentation are sometimes annoying, but frankly these are such
minor issues I wonder
why people waste their time venting about them given the source code's
state.

On Tue, Mar 31, 2009 at 7:59 AM, Laurent Desnogues <
laurent.desnogues@gmail.com> wrote:

> On Tue, Mar 31, 2009 at 12:38 AM, Lennart Sorensen
> <lsorense@csclub.uwaterloo.ca> wrote:
> > On Mon, Mar 30, 2009 at 04:15:14PM -0600, M. Warner Losh wrote:
> >> With editors like emacs, this isn't an issue.
> >
> > Who gives a @#$ what emacs does.
>
> Ha at last!  vi was put in the original document, then someone mentions
> emacs and then some insults.  This finally becomes interesting.
>
>
> Laurent
>
>
>

[-- Attachment #2: Type: text/html, Size: 1740 bytes --]

  reply	other threads:[~2009-03-31 12:59 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
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 [this message]
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=60cad3f0903310558j554d6906q6f1244fd8a7449aa@mail.gmail.com \
    --to=digit@google.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).