Garrett Rooney <rooneg@electricjellyfish.net> writes:
> Kristian Hogsberg wrote:
> > Hi all,
> > I've recently installed subversion 0.24.2 - it's working nicely, and
> > it really is a great tool. Looking around in the source tree, I
> > discovered the ruby bindings, but I couldn't figure out how to build
> > them and I found out that they weren't even mentioned in build.conf.
> > Do I have to write my own Makefile for this, and are they at all
> > up-to-date?
>
> If you wanted to try to build them, you'd use the extconf.rb in the
> bindings/ruby directory...
Ah, I missed that one. I'll give it a try.
> But that would be rather futile, as they are horribly out of date.
> If you're looking for something to do, you could try to update them,
> or better yet, try to write us some SWIG based ruby bindings, which
> would have a better chance of staying up to date.
Yeah, I realize the SWIG bindings are easier to maintain, but I looked
at the python bindings and I wasn't too impressed. The subversion C
API appears to be object-oriented C, in much the same way as the Gtk+
toolkit, but the python bindings doesn't really reflect this. For
example, the following code (from svnlook.py)
txn_ptr = fs.open_txn(self.fs_ptr, txn, pool)
should be (in my opinion, of course):
txn_obj = fs_obj.open_txn(txn, pool)
where the pointers are wrapped in python objects so you can say
obj.method(args) instead of method(obj, args) as you would in C. I've
browsed through the ruby bindings and they do this already. After
all, I'm only planning to use the bindings for some server-side
scripting, so I'll only need to update bindings for core, fs and
repos... I guess?
thanks,
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 1 17:37:44 2003