From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/5] qapi: avoid reserved word restrict
Date: Wed, 01 Aug 2012 08:45:23 +0200 [thread overview]
Message-ID: <5018D083.1050409@redhat.com> (raw)
In-Reply-To: <CAAu8pHuDuHq=yF0zenWXMGk+zdwqnF6qzQDJsFD10QVKt8AaRQ@mail.gmail.com>
Il 31/07/2012 22:38, Blue Swirl ha scritto:
>> > It's a whole lot of churn though, and clobbers the history for most QMP
>> > functions. It also seems like a strange thing for clang to complain about...
> Not really, it's just C99:
> http://en.wikipedia.org/wiki/Restrict
>
> Prefixing would solve also future problems: 'if', 'auto', maybe
> 'static' can make sense for network options (as compared to DHCP) one
> day etc.
>
We could detect C keywords and prefix (or suffix) an underscore
automatically.
Paolo
next prev parent reply other threads:[~2012-08-01 6:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 16:04 [Qemu-devel] [PATCH 0/5] Clang patches blauwirbel
2012-07-30 16:04 ` [Qemu-devel] [PATCH 1/5] sparc: fix floppy TC line setup blauwirbel
2012-07-30 16:04 ` [Qemu-devel] [PATCH 2/5] sparc: fix expression with uninitialized initial value blauwirbel
2012-07-30 16:13 ` Peter Maydell
2012-07-30 16:59 ` Andreas Färber
2012-07-30 17:09 ` Peter Maydell
2012-07-30 17:20 ` Blue Swirl
2012-07-30 17:57 ` Peter Maydell
2012-07-30 16:04 ` [Qemu-devel] [PATCH 3/5] qapi: avoid reserved word restrict blauwirbel
2012-07-31 7:28 ` Paolo Bonzini
2012-07-31 12:58 ` Luiz Capitulino
2012-07-31 16:56 ` Blue Swirl
2012-07-31 18:55 ` Michael Roth
2012-07-31 20:38 ` Blue Swirl
2012-07-31 22:30 ` Michael Roth
2012-08-01 6:45 ` Paolo Bonzini [this message]
2012-08-01 17:35 ` Blue Swirl
2012-08-01 0:01 ` Anthony Liguori
2012-07-30 16:04 ` [Qemu-devel] [PATCH 4/5] user: fix accidental AREG0 use blauwirbel
2012-07-30 16:04 ` [Qemu-devel] [PATCH 5/5] configure: disable a few Clang compiler warnings blauwirbel
2012-07-30 16:56 ` Stefan Weil
2012-07-30 17:23 ` Blue Swirl
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=5018D083.1050409@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.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.