Re: [Xen-devel] Compile error when including xenctrl.h

To:	<dassing@xxxxxxxxxxxxxx>, <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Compile error when including xenctrl.h
From:	Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date:	Tue, 12 Jun 2007 08:50:25 +0100
Delivery-date:	Tue, 12 Jun 2007 00:45:55 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<466E36A2.2080504@xxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcesxlYElFmm6Bi5Edya8gAWy6hiGQ==
Thread-topic:	[Xen-devel] Compile error when including xenctrl.h
User-agent:	Microsoft-Entourage/11.3.3.061214

On 12/6/07 07:01, "Reiner Dassing" <dassing@xxxxxxxxxxxxxx> wrote:

> these errors could be solved.
> 
> Any comments?

I think it's the const before the * that is bogus. It's probably meant to be
after the *, otherwise it probably can be interpreted as a duplicate of the
const before the type name. That const can be removed entirely in fact, as
the const-ness of the pointer itself is quite uninteresting: it's the thing
pointed at that we care about the const-ness of.

So, e.g., I'll change it to const xc_error *xc_get_last_error(void);

 -- Keir

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Compile error when including xenctrl.h