From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v2] RFC: Automatically check xen's public headers for C++ pitfalls.
Date: Thu, 26 Feb 2015 19:49:22 +0200 [thread overview]
Message-ID: <54EF5CA2.8050807@bitdefender.com> (raw)
In-Reply-To: <20150226170154.GB43834@deinos.phlegethon.org>
On 02/26/2015 07:01 PM, Tim Deegan wrote:
> +#ifdef __cplusplus
> +/* 'private' is a keyword in C++, so we have to use a different name for
> + * private state there. Leaving the C name alone to avoid unnecessary
> + * pain for the existing users. */
> +#define XEN_RING_PRIVATE pvt
> +#else
> +#define XEN_RING_PRIVATE private
> +#endif
Are there likely to be many users outside of the ones using that code
with mem_event? Because if there aren't, there are much more drastic
changes happening in Tamas' pending series, so perhaps seen that way the
change becomes more acceptable.
Thanks,
Razvan
next prev parent reply other threads:[~2015-02-26 17:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 13:11 [PATCH] RFC: Make xen's public headers a little friendlier for C++ Tim Deegan
2015-02-26 14:09 ` Jan Beulich
2015-02-26 15:22 ` Tim Deegan
2015-02-26 15:39 ` Jan Beulich
2015-02-26 16:11 ` [PATCH v2] RFC: Automatically check xen's public headers for C++ pitfalls Tim Deegan
2015-02-26 16:28 ` Tim Deegan
2015-02-26 16:43 ` Andrew Cooper
2015-02-26 16:47 ` Jan Beulich
2015-02-26 17:01 ` Tim Deegan
2015-02-26 17:49 ` Razvan Cojocaru [this message]
2015-02-26 19:22 ` Tim Deegan
2015-02-26 20:31 ` Don Slutz
2015-02-27 8:00 ` Jan Beulich
2015-02-26 16:49 ` David Vrabel
2015-03-05 11:25 ` Tim Deegan
2015-03-05 11:35 ` Ian Campbell
2015-03-05 11:41 ` Jan Beulich
2015-03-05 11:55 ` Ian Campbell
2015-03-05 12:13 ` Wei Liu
2015-03-05 12:34 ` Ian Campbell
2015-03-05 12:16 ` Tim Deegan
2015-03-12 10:03 ` Tim Deegan
2015-03-12 10:14 ` Ian Campbell
2015-03-12 11:16 ` Tim Deegan
2015-03-12 10:57 ` Jan Beulich
2015-02-26 16:24 ` [PATCH v3] " Tim Deegan
2015-02-26 20:28 ` Don Slutz
2015-02-27 10:05 ` Tim Deegan
2015-02-27 8:36 ` Jan Beulich
2015-02-27 9:22 ` Tim Deegan
2015-02-27 9:34 ` Jan Beulich
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=54EF5CA2.8050807@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.