Feature request 4565 [1] concerns exposing the libxml2 _private member in libxml-ruby. This looks doable, but I wonder if anyone who knows more about libxml2 than I do has any thoughts? One potential problem I can think of is that libxslt apparently makes use of _private, so it might open up a can of worms when they're used together...?
Thanks, Ross [1]: http://rubyforge.org/tracker/index.php?func=detail&aid=4565&group_id=494&atid=1974 -- Ross Bamford - [EMAIL PROTECTED] _______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
