I have been on vacation. My contributions to date have been minor, but I am have a vested interest in getting the memory model problem resolved. I did something similar for the Berkeley DB library, which had a completely faulty binding approach and rewrote it entirely and now is completely memory stable and essentially fault-free.
My biggest problem is the documentation for libxml2 seems to rather suck in relation to the complexity of the interface. So I have not been able to get my head around the options for solving this problem. My past (long ago) uses of SWiG for other purposes left much to be desired, so I have no opinion about that. The first thought I have is to look for another language binding that works well and see if that approach can be made to work for Ruby. This does seem to be the best XML solution, so getting it all fixed up seems like a really good idea. It seems to be bigger than one person can manage on a part time basis, but there needs to be a unified vision of how to approach the problem. Dan On Jul 12, 2007, at 13:03, TRANS wrote: > I see that Ross Bramford is not even listed as a project member any > more --let alone the maintainer. So that means things fall back to > Sean Chittenden -- but is he around? I see three other members listed: > > Dan Janowski > Laurent Sansonetti > Pat Eyler > > Are any of you guys around? > > I fear there's no one at the hem again, but there are still important > issues that need to be addressed. From the looks of it there hasn't > been a commit since January, though there have been patches offered up > on this list since then. > > What's the word? > > T. > _______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
