From: malc <av1474@comtv.ru>
To: Juan Quintela <quintela@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 3/4] Use C99 initializers for audio_option
Date: Tue, 28 Jul 2009 21:39:54 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0907282136470.5501@linmac.oyster.ru> (raw)
In-Reply-To: <m3bpn4bu1t.fsf@neno.mitica>
On Tue, 28 Jul 2009, Juan Quintela wrote:
> malc <av1474@comtv.ru> wrote:
> > On Tue, 28 Jul 2009, Juan Quintela wrote:
> >
> >> malc <av1474@comtv.ru> wrote:
> >> > On Mon, 27 Jul 2009, Juan Quintela wrote:
> >> >
> >> > I'd prefer:
> >> >
> >> > { .name = "DAC_SIZE_IN_USEC",
> >> > .tag = AUD_OPT_BOOL,
> >> > .valp = &conf.size_in_usec_out,
> >> > .descr = "DAC period/buffer size in microseconds (otherwise in frames)" },
> >> > { ...
> >> >
> >> > And likewise elsewhere.
> >>
> >> I tried to be consistent with the qdev patches, they add all its "arrays
> >> of structures" this way (it is one of the bigger users of the feature
> >> that I saw).
> >
> > Let's look at original example:
> >
> > + {
> > + .name = "DAC_SIZE_IN_USEC",
> > + .tag = AUD_OPT_BOOL,
> > + .valp = &conf.size_in_usec_out,
> > + .descr = "DAC period/buffer size in microseconds (otherwise in frames)"
> > + },{
> >
> > It's internally inconsistent (begins with a bsd style ends with k&r,
> > and on top of that without space after comma). Should either be done
> > the way i mentioned earlier or with:
> >
> > {
> > ...
> > },
> > {
> > }
> >
> > And i much prefer the former.
>
> I was trying to be consistent with rest of qemu:
>
> (simple-config-7*)$ find . -name "*.[ch]" | xargs grep " },{$" | wc -l
> 42
> (simple-config-7*)$ find . -name "*.[ch]" | xargs grep " }, {$" | wc -l
> 18
Alrighty then:
qemu$ find . -name "*.[ch]" | xargs grep " },$" | wc -l
10294
>
> I don't mean going one way or the other, but I would like that everbody
> decided what was the "right" position of the braces. If possible, not
> one style by directory.
Once again - i do understand the motivation, i just don't see much point.
I just happen to like the code i maintain to look internally consistent.
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-07-28 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 20:23 [Qemu-devel] [PATCH 0/4] Use C99 struct initializers in audio/* Juan Quintela
2009-07-27 20:23 ` [Qemu-devel] [PATCH 1/4] Use proper struct initializers and remove INIT_FIELD() macro Juan Quintela
2009-07-27 21:03 ` malc
2009-07-27 21:07 ` Anthony Liguori
2009-07-27 22:57 ` [Qemu-devel] " Paolo Bonzini
2009-07-27 23:02 ` [Qemu-devel] " Anthony Liguori
2009-07-28 16:54 ` malc
2009-07-28 17:13 ` [Qemu-devel] " Juan Quintela
2009-07-28 17:23 ` malc
2009-07-27 20:23 ` [Qemu-devel] [PATCH 2/4] use C99 initializers for audio_pcm_ops Juan Quintela
2009-07-27 21:07 ` malc
2009-07-27 20:23 ` [Qemu-devel] [PATCH 3/4] Use C99 initializers for audio_option Juan Quintela
2009-07-27 21:10 ` malc
2009-07-27 22:20 ` [Qemu-devel] " Juan Quintela
2009-07-28 8:03 ` Gerd Hoffmann
2009-07-28 8:22 ` Juan Quintela
2009-07-28 16:48 ` malc
2009-07-28 17:23 ` Juan Quintela
2009-07-28 17:39 ` malc [this message]
2009-07-27 20:23 ` [Qemu-devel] [PATCH 4/4] use C99 initializers for all audio/* Juan Quintela
2009-07-27 21:11 ` malc
2009-07-27 20:30 ` [Qemu-devel] Re: [PATCH 0/4] Use C99 struct initializers in audio/* 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=Pine.LNX.4.64.0907282136470.5501@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).