[libxml-devel] Pushing libxml forward - a new 0.6.0 release

Charlie Savage cfis at savagexi.com
Wed Jul 2 22:25:29 EDT 2008


libxml-devel at rubyforge.org

Hi everyone,

As you might have guessed by the recent email traffic, I've dived into 
the libxml (and libxslt) ruby bindings since I need them MapBuzz.

Thanks to Sean for developing the bindings and Dan for reworking the 
memory model.  From what I can tell, the library is actually is pretty 
good shape, there just a few little gotchas left that people are running 
into.

So to get things moving again, I took the liberty to push out a new 
release of libxml-ruby, 0.6.0.  It fixes a number of memory issues and 
adds Windows support.  I am sure there are still remaining memory 
issues.  If everyone can update their gems and reports any bugs they run 
into, I'll give it a try and fixing them.

I also have a new version of libxslt-ruby, but first need commit rights 
to push a release.

Thanks,

Charlie

----------
Changes:

* Fixed memory allocation errors in Windows.  On Windows, it is 
essential that the same library that allocates memory must free it. 
Thus ALLOC calls must be matched to ruby_xfree calls, which they were 
not.  In addition, in one case Ruby was allocating memory to be freed by 
libxml.  On Windows, that's a segmentation fault.  On Linux it might 
fly, but still seems like a bad idea.

* Fixed segmentation fault in xml reader expand (same xml tree freed twice)

* Applied a number of patches from Tom Bagby, including fixes for xpath 
segmentation faults and fixes for various memory leaks

* Cleaned up a number of compiler warnings

* Renamed libxml_so.so to libxml_ruby.so (same for xslt).  That wasn't 
actually my original intention, but um, it kind of sort of happened.  It 
should not be noticeable from an end-user perspective.

* Added rake files for building with MingW

* Added rake files for packing gems.  Note that I did this outside the 
existing rake tasks because I didn't see how they were actually building 
the gems.

* Cleaned up the tests and added a few more based on bug reports from 
the Tracker and mailing list.

* Cleaned out the patch queue and went through about 1/2 the bug list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://rubyforge.org/pipermail/libxml-devel/attachments/20080702/51993172/attachment.bin>


More information about the libxml-devel mailing list