From: Jeremy Katz <katzj@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: [PATCH] libxen-3.0 (libxc rewrite)
Date: Tue, 22 Mar 2005 11:25:48 -0500 [thread overview]
Message-ID: <1111508748.6797.4.camel@bree.local.net> (raw)
In-Reply-To: <4240400F.3040805@us.ibm.com>
On Tue, 2005-03-22 at 09:55 -0600, Anthony Liguori wrote:
> Jeremy Katz wrote:
> >On Tue, 2005-03-22 at 09:18 -0600, Anthony Liguori wrote:
> >>Do you have a suggestion for an alternative? I know there are a number
> >>of binding-generators but I thought Pyrex was the most widely used.
> >
> >Pyrex is probably the most generally used -- the stuff pygtk uses is
> >nice, but not very general.
> >
> >In most cases, though, bindings done by hand end up being higher quality
> >than something that's just being generated.
> >
> I was afraid that that would be your answer.
>
> I would really like to automatically generate the bindings. There is
> more C code in the current libxc/libxu python bindings than all of vm-tools.
That doesn't make it bad :) You're just moving where the code is to
another place by generating the bindings.
> gcc4 is still a bit off and I imagine that Pyrex will be updated as
> needed. If it ever proves to be painful to deal with, I'll break down
> and add bindings by hand. Does that seem like a reasonable plan moving
> forward?
gcc4 isn't that far off. It's in the Fedora development tree and we're
using it to compile everything now. See Rik's multiple patches to fix
warnings that pop up with gcc4. And counting on Pyrex being fixed based
on the complete lack of response to questions on this topic may be
wishful thinking. Maybe I'll look at Pyrex a little this afternoon and
see if I can figure out how to fix what it's doing.
Jeremy
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
next prev parent reply other threads:[~2005-03-22 16:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 9:01 [PATCH] libxen-3.0 (libxc rewrite) Ian Pratt
2005-03-22 15:03 ` Anthony Liguori
[not found] ` <1111504492.20157.26.camel@bree.local.net>
2005-03-22 15:18 ` Anthony Liguori
2005-03-22 15:31 ` Jeremy Katz
2005-03-22 15:55 ` Anthony Liguori
2005-03-22 16:25 ` Jeremy Katz [this message]
2005-03-22 21:58 ` Jeremy Katz
2005-03-22 22:18 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 17:21 Ian Pratt
2005-03-22 17:31 ` Anthony Liguori
2005-03-22 16:25 Ian Pratt
2005-03-22 16:00 Ian Pratt
2005-03-22 16:13 ` Anthony Liguori
2005-03-22 16:29 ` Nivedita Singhvi
2005-03-22 16:34 ` Anthony Liguori
2005-03-22 16:39 ` Steven Hand
2005-03-22 15:13 Ian Pratt
2005-03-21 21:25 Anthony Liguori
2005-03-22 3:33 ` Jacob Gorm Hansen
2005-03-22 4:24 ` Anthony Liguori
2005-03-22 19:28 ` Adam Heath
2005-03-22 20:12 ` Jacob Gorm Hansen
2005-03-22 11:02 ` Christian Limpach
2005-03-22 15:04 ` Anthony Liguori
2005-03-22 16:01 ` Christian Limpach
2005-03-22 16:06 ` Anthony Liguori
2005-03-22 16:13 ` Christian Limpach
2005-03-22 16:21 ` Anthony Liguori
2005-03-22 16:41 ` Christian Limpach
2005-03-22 17:05 ` Anthony Liguori
2005-03-22 17:28 ` Keir Fraser
2005-03-22 17:32 ` Ronald G. Minnich
2005-03-22 17:47 ` Christian Limpach
2005-03-22 17:53 ` Anthony Liguori
2005-03-22 13:50 ` Keir Fraser
2005-03-22 15:16 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1111508748.6797.4.camel@bree.local.net \
--to=katzj@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.