From: Anthony Liguori <anthony@codemonkey.ws>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: qemu-devel@nongnu.org, bifferos <bifferos@yahoo.co.uk>
Subject: Re: [Qemu-devel] [PATCH] Add support for r6040 NIC
Date: Wed, 31 Aug 2011 13:48:34 -0500 [thread overview]
Message-ID: <4E5E8202.1040109@codemonkey.ws> (raw)
In-Reply-To: <20110831175934.GA17959@zapo>
On 08/31/2011 12:59 PM, Edgar E. Iglesias wrote:
> On Wed, Aug 31, 2011 at 11:06:11AM -0500, Anthony Liguori wrote:
>> On 08/31/2011 09:35 AM, malc wrote:
>>> On Wed, 31 Aug 2011, Anthony Liguori wrote:
>>>
>>>> Upper case field names are not okay. If you think coding style isn't clear,
>>>> that's a bug in coding style.
>>>
>>> Sez hu? Coding style is garbage that should be thrown out of the window.
>>> As for looking, yeah, i'm looking at usb with it's lovely hungarian
>>> fields, should we stampede to "fix" it?
>>>
>>> If the one who's going to maintain the code is fine with whatever naming
>>> is used so be it.
>>
>> No. That's how we got into the coding style mess we're in in the
>> first place.
>
> TBH, the codingstyle in QEMU is the least of "problems" we are facing.
> We've got lack of documentation, lack of tests, lack of contributors,
> etc, etc. IMO, those bring codingstyle issues into the pretty much
> neglectable space.
I don't think we lack contributors. Documentation and tests are really
about discipline. If we can't even be bothered to maintain consistency
in variable naming, do you really expected that we can be disciplined in
writing documentation and tests?
Is the next argument going to be that every subsystem should be able to
have its documentation in it's preferred natural language such that the
documentation for the block layer is in Esperanto?
Consistent coding style makes the tree a single code base, instead of a
bunch of independent islands. This encourages sharing code and ideas
across subsystems. Too often, we reproduce the same thing and over
again in different subsystems (and even different machine architectures).
Regards,
Anthony Liguori
>
> I think we should throw out everything from CS beyond the details of
> spaces and braces. Maybe keep the 80 char limit.
>
> We should ofcourse refer to the C and other specs regarding correctness,
> like the _t thing, but those are not really stylistic issues. Those are
> bugs.
>
> my 5 cents
>
> Cheers
>
next prev parent reply other threads:[~2011-08-31 18:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 1:05 [Qemu-devel] [PATCH] Add support for r6040 NIC bifferos
2011-08-31 1:17 ` Anthony Liguori
2011-08-31 1:30 ` malc
2011-08-31 1:59 ` Anthony Liguori
2011-08-31 13:17 ` malc
2011-08-31 13:30 ` Anthony Liguori
2011-08-31 13:39 ` malc
2011-08-31 13:40 ` Anthony Liguori
2011-08-31 13:51 ` malc
2011-08-31 14:29 ` Anthony Liguori
2011-08-31 14:35 ` malc
2011-08-31 16:06 ` Anthony Liguori
2011-08-31 16:24 ` malc
2011-08-31 18:35 ` Blue Swirl
2011-08-31 18:37 ` malc
2011-08-31 17:59 ` Edgar E. Iglesias
2011-08-31 18:46 ` Blue Swirl
2011-08-31 18:58 ` Edgar E. Iglesias
2011-08-31 18:48 ` Anthony Liguori [this message]
2011-08-31 19:12 ` Edgar E. Iglesias
2011-08-31 19:18 ` Edgar E. Iglesias
2011-08-31 19:23 ` Anthony Liguori
2011-08-31 19:52 ` Blue Swirl
2011-08-31 18:30 ` Blue Swirl
2011-08-31 21:23 ` bifferos
2011-09-01 7:39 ` Markus Armbruster
2011-09-01 21:49 ` Anthony Liguori
2011-09-03 9:44 ` Blue Swirl
2011-09-01 10:42 ` Gerd Hoffmann
2011-08-31 13:35 ` bifferos
2011-08-31 20:03 ` [Qemu-devel] [PATCH v2] " bifferos
2011-09-01 8:43 ` [Qemu-devel] [PATCH] " Avi Kivity
2011-09-01 20:02 ` bifferos
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=4E5E8202.1040109@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=bifferos@yahoo.co.uk \
--cc=edgar.iglesias@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 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.