there are still a number of fundamental problems with libxml-ruby - mostly to do with the fact that libxml and ruby are constantly fighting over memory management and the like.
Ross - Could you summarize these issues, and exactly what is going wrong where? It would be extremely helpful as a guide to anyone who has time to dig into the issue.
I did a lot of work on SWIG's ruby support, so have a good feeling for the various memory issues that can arise. But I know nothing about libxml's api or memory management, or how the ruby bindings interact with it.
Also, does the patch from open street map fix the issue?
The Windows issue matters, too, but since I've been lucky enough to avoid Windows almost entirely in my professional life for several years now I don't really know the platform well enough to handle this, and frankly I'm unwilling to take the time to learn for the sake of compatibility on one project. Another thing that needs to be done.
I can solve the windows issues. I have a patch to fix up memory allocation on windows, and with my experience with ruby-prof, I can easily create a win32 gem.
A lot of good work was done on libxml-ruby, as recently as Laurent's reader contributions, and it'd be a shame to see things grind to a halt. I'm willing to help make sure they don't, but what we really need is people involved in all that other stuff I talked about above.
Thanks, Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
