From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: pointers in public headers Date: Fri, 25 Aug 2006 16:40:38 +0100 Message-ID: <44EF3616.76E4.0078.0@novell.com> References: <44EF2FA2.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >I don't know enough about the scheme you are implementing to be able to >comment. You could look at the patches posted earlier today. In short, it simply takes the public headers and replaces all occurrences of 'long' in there with 'int' (while obviously properly renaming everything to not result in name collisions) - whether other types are used that need adjustment will need to be seen later. >I mean API compat from the p.o.v. of guests -- any macro would only >be defined as other than a plain pointer for Xen and your scripts, which >would presumably know what they're doing and avoid compile warnings. Yes, if the whole Xen tree (including the tools) is not of concern, then this would work - Xen (and implicitly the conversion script) would see an unsigned long there then, which match all other places needing conversion. Jan