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.
SWIG is fine - but it isn't a magic bullet that will solve the issue. It does offer once nice feature, you can set it up so that it returns the same Ruby object for a given C object (as opposed to having 4 ruby objects all point to the same C object). But SWIG is not the easiest thing to use, and if the bindings already exist anyway, I'd probably just stick with them (unless they cover such a small part of the api that it would be worth autogenerating the rest).
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.
Maybe Python? Although it uses reference counting, not a GC, so maybe not appropriate.
Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
