[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ctypes + Subversion + a few high level python modules = really great python bindings

From: Sage La Torra <sagelt_at_gmail.com>
Date: 2007-04-10 15:53:51 CEST

On 4/10/07, Giovanni Bajo <rasky@develer.com> wrote:
> I can't comment on Ruby DL or Perl Inline::C (which doesn't exactly look like
> ctypes to a quick look but I'll let expert comment), but Python ctypes looks
> like the perfect solution for wrapping Subversion C API.

It isn't _exactly_ like ctypes, but it's one of a few different Perl/C
integration mechanisms that can offer the same functionality, or near
enough to it. Additionally, at least in my experience, SWIG can work
better with Perl since the Perl interpreter is written (mostly) in C,
so most Perl types can be very easily mapped to C types. Perl/C
integration is a long topic that can get messy, but in general not as
messy as many other cross language interfaces,

This is a little off topic, but I wouldn't worry about Perl bindings,
as long as the existing ones don't go away. There's a number of svn
modules on CPAN, and while I don't know much about the internals of
most of them, I would wager they use the SWIG bindings and build a
nice, high-level interface.

My feeling is that since the Perl community (or people in the overlap
between svn folks and perl folks) have made a high level binding, so
as long as we don't completely get rid of SWIG there won't be any
negative side effects there.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 10 15:54:08 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.