WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] size_t and printk and Xen

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] size_t and printk and Xen
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 12 Oct 2008 18:57:33 +0100
Cc:
Delivery-date: Sun, 12 Oct 2008 10:58:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3924720e-82a1-4429-9951-14731d76b5a2@default>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckslABiPy7FZJiHEd22twAWy6hiGQ==
Thread-topic: [Xen-devel] size_t and printk and Xen
User-agent: Microsoft-Entourage/11.4.0.080122
On 12/10/08 18:44, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

>> I'm no particular fan of size_t in hypervisor interfaces
>> though. So, for
>> example, switching xmalloc() interfaces to use unsigned int
>> instead would be
>> fine by me, and this would sidestep the issue perhaps?
> 
> I think C99 size_t may have compile-time type-checking uses so
> I'd be hesitant to remove it entirely.

Can you give a concrete example of how it helps us to use it within the
xmalloc interfaces? As far as I'm aware it's not useful at all, but I could
certainly be wrong as this aspect of the C spec is not something I've ever
really investigated.

 -- Keir



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