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

RE: [Xen-devel] [PATCH 1/3] Typesafe allocators

  • To: "Rusty Russell" <rusty@xxxxxxxxxxxxxxx>, "Xen Mailing List" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 2 Feb 2005 11:31:20 -0000
  • Delivery-date: Wed, 02 Feb 2005 11:33:56 +0000
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
  • Thread-index: AcUI5V2OxM46yI0eSY2Xi4QNPS+UUwANO98Q
  • Thread-topic: [Xen-devel] [PATCH 1/3] Typesafe allocators

> While reading through the sources, I noticed that you've already
> diverged from "kmalloc" to xmalloc, so I thought it worth trying a
> typesafe allocator (something I have long missed in Linux).

We like the concept of this patch (and the other two), but renaming
xmalloc to 'new' has triggered all sorts of c++ antibodies. In
particular, its hard to grep for 'new'. 

Can we just keep the xmalloc name but make it type safe, and add


This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
Xen-devel mailing list



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