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

Re: Perl swig bindings starting to smell

From: John Peacock <jpeacock_at_rowman.com>
Date: 2007-01-11 17:03:56 CET

Miller, Eric wrote:
> Is anyone working on, or interested in working on bringing the perl swig
> bindings up to date?
>
> They look like they are well past their expiration date.

Are you using trunk code or 1.4.x? The reason I ask is that there has
been a lot of activity to improved both the interface (adding new
methods that have been added) as well as the documentation. If the Perl
bindings seem stale, it is primarily because there isn't a core
developer to champion them at the moment. The nature of SWIG (as I
understand) it is that mostly maintenance work needs to be done (making
sure that new interfaces are added to the Perl-level exports), since
SWIG is doing all of the heavy lifting already. I know that there were
a bunch of commits in the middle of December to make sure that SVK had
access to the faster ra_replay code.

Nik Clayton was working with adding named parameter support (but I've
lost track of where that stands). Mattias Engdegard recently submitted
a patch to add a bunch more client functions, but it doesn't appear to
have been committed. I don't think your characterization of the code is
really all that accurate. It's clear that the core committers need to
get back to the practice of keeping on top of submitted patches.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 11 20:40:41 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.