From: Anthony Liguori <anthony@codemonkey.ws>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jes Sorensen <jes@sgi.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch 1/2] machine struct - use C99 initializers
Date: Mon, 06 Oct 2008 10:23:02 -0500 [thread overview]
Message-ID: <48EA2D56.4040908@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.1.00.0810061724470.22125@pacific.mpi-cbg.de.mpi-cbg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Mon, 6 Oct 2008, Jes Sorensen wrote:
>
>
>> Johannes Schindelin wrote:
>>
>>
>>> P.S.: before somebody says that GCC is C99 compliant: search the
>>> mailing list for the Beos GCC2 issue which was mentioned not long ago.
>>>
>> GCC is sufficiently C99 compliant to handle this style of initializers.
>> Maybe it's not C99 compliant enough for other stuff, but on this front
>> it does just fine.
>>
>
> I just wish you would have researched a bit better. (And no, adding to
> the pile does not make your intention any better.)
>
> Nobody ever disputed that _you_ have no problem with your patch.
>
FWIW, we already use this feature in QEMU. Is there a specific compiler
you're concerned about? QEMU won't compile on a compiler that doesn't
support this construct right now and hasn't been able to for a very long
time (years, if ever).
Regards,
Anthony Liguori
> Sigh,
> Dscho
>
>
next prev parent reply other threads:[~2008-10-06 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:09 [Qemu-devel] [patch 1/2] machine struct - use C99 initializers Jes Sorensen
2008-10-06 15:05 ` Johannes Schindelin
2008-10-06 15:03 ` Jes Sorensen
2008-10-06 15:26 ` Johannes Schindelin
2008-10-06 15:23 ` Anthony Liguori [this message]
2008-10-06 20:22 ` Ronan Keryell
2008-10-06 22:46 ` Andreas Färber
2008-10-06 23:07 ` Paul Brook
2008-10-06 23:38 ` M. Warner Losh
2008-10-07 13:50 ` Paul Brook
2008-10-07 7:13 ` Jes Sorensen
2008-10-26 15:17 ` Andreas Färber
2008-10-06 15:30 ` Thiemo Seufer
2008-10-07 20:34 ` 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=48EA2D56.4040908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Johannes.Schindelin@gmx.de \
--cc=jes@sgi.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).