From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: Xen tools (libxs, xenstore) and C++ Date: Tue, 22 Jan 2013 17:35:03 +0200 Message-ID: <50FEB1A7.70207@gmail.com> References: <50FEAD68.1000604@gmail.com> <50FEAF9C.609@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <50FEAF9C.609@citrix.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: Andrew Cooper Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org >> /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 token >> >> where the DEFINE_RING_TYPES(mem_event, mem_event_request_t, >> mem_event_response_t); macro is being expanded in mem_event.h. This one was cause because ring.h was using the C++ keyword 'private'. > I think C++ friendliness is a good idea (especially as I think I might > be needing C++ friendliness at some point in the not-too-distant future) OK, hopefully I'll manage to patch these headers tomorrow (of course, = there are others...). Cheers, Razvan