[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AckslABiPy7FZJiHEd22twAWy6hiGQ==
  • Thread-topic: [Xen-devel] size_t and printk and Xen

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.