[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: Daniel Rall <dlr_at_collab.net>
Date: 2007-01-17 20:23:06 CET

On Wed, 17 Jan 2007, John Peacock wrote:

> Nik Clayton wrote:
> >I see you've committed 2646. Are you planning on closing the ticket too
> >(I've not poked around tigris.org yet, so I need to find out how to do
> >that).
>
> I don't think us mortals have the appropriate rights to close tickets.
> I was only planning on adding a comment to the bugtracker that it had
> been applied on the branch and whoever actually merged it to trunk would
> probably be able to also close the ticket.

You need the appropriate role in the Subversion project on tigris.org,
which I've granted to you both.

...
> >The major change that I've started is the one that introduces named
> >parameters (and makes some of them optional if we can have sensible
> >defaults for them).
>
> And I'm perfect happy to review those changes, but don't expect much new
> code from me (unless I get an itch I can't scratch while building the
> tests). Initially, I'll focus on getting the two existing patches ready
> to merge to trunk; I'll stay out of your way on the named parameters piece.
...

How does the introduction of named parameters impact backwards
compatibility? (I assume it doesn't have to.)

Sounds like a breakdown of who's doing what is forming:

- John has committed some outstanding patches against the bindings,
which will be cleaned up a touch more.

- Nik is helping out with that cleanup, and will work on API named
parameter support.

- John will enhance the test suite.

Re-writing 'svn' in Perl and excercising it (perhaps using portions of
the existing cmdline test suite?) sounds like a really good test
suite and example of how to use the bindings.

  • application/pgp-signature attachment: stored
Received on Wed Jan 17 20:23:23 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.