From: Evan M. <ma...@cs...> - 2002-08-07 22:34:26
|
Darrin Thompson wrote: > Did your decision to not use SWIG take into consideration the recent > developments there? From what I've read on the english ruby-talk list, > SWIG 1.3 is turning into a really excellent tool and the ruby to c code > generator is excellent. Perhaps you all should reconsider? > > http://swig-jp.dyndns.org/ <- Japanese. I don't know what it actually > says. :-) I believe one of their design decisions was to do things by hand. If you're going to use autogeneration, GTK provides a datafile (gtk.defs) that describes all of the C functions in a structured form that is parsable into generated wrappers. That's how PyGTK [Python] does it, for example (I believe that James, the guy behind PyGTK, is actually responsible for it). I wrote a small parser for that file a while back but there is still a lot of internal work to do-- the GObject <-> Ruby object stuff probably needs to be done by hand. |