From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: [PATCH] libxc, libxenstore: make the headers C++-friendly Date: Tue, 22 Jan 2013 19:21:50 +0200 Message-ID: <50FECAAE.40104@gmail.com> References: <93e5f6cf98d2ae3539db.1358873051@rcojocaru.dsd.ro> <50FED22102000078000B86C8@nat28.tlf.novell.com> <50FEC73B.7020208@gmail.com> <50FED67602000078000B86EA@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <50FED67602000078000B86EA@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel List-Id: xen-devel@lists.xenproject.org > Not exactly - with all of this being macros, the _consumer_ of > DEFINE_RING_TYPES() could define private to rprivate (or > whatever is being liked best), with the respective uses of the > other macros using that field suitably placed inside the scope > of that #define. All I have to do is #include and I get this build error = (with g++): /usr/include/xen/mem_event.h:71:1: error: expected =91;=92 after union definition /usr/include/xen/mem_event.h:71:1: error: expected =91:=92 before =91;=92 t= oken It goes away after renaming 'private' to something else (that's not a = C++ keyword). Not much room to maneuver around it from C++ code. Cheers, Razvan Cojocaru