On 8/30/07, Eric Gillespie <epg@pretzelnet.org> wrote:
> Greg Stein <gstein@gmail.com> writes:
>
> > The ctypes binding requires manual work each time a new API is
> > introduced? i.e. a new binding func must be written?
>
> No, the low-level binding is generated fully automatically, which
> is more than can be said for Swig. I spend a lot of time on
> typemaps with the Swig binding :(.
>
> Now, the high-level layer is different, but that's 100% value-add
> over what Swig gives us anyway. It would not be less work with
> the Swig binding.
>
> --
> Eric Gillespie <*> epg@pretzelnet.org
>
Exactly. The actual API function bindings are automatic, the classes
built on top are icing on the cake, so to speak. The idea of the
classes is to give the average user (if such a beast exists) a handy
python-ish wrapper for typical tasks, like updating, committing,
reverting, getting log messages and so on. Sorry I wasn't more clear
on that.
Sage
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 31 01:56:15 2007