On Fri, 14 Apr 2006 13:24:41 +0100, zdennis <[EMAIL PROTECTED]> wrote:
> A while back you posted: > > http://rubyforge.org/pipermail/libxml-devel/attachments/20051230/778cd254/libxml-x.obj > > And I know Mark VanHolstyn posted some pure-ruby stuff with his patches > also. Will this ruby-addition to the api be included with > ruby-libxml distribution? If not, I want to petition that it is, even if > it's not included by "require 'libxml'" be default, it > would be nice to say "require 'libxml/ext'" or something, because the > functionality (although some is not apart of the libxml > binding itself, is really nice to have, and it would make upgrading > libxml versions so much easier. > I'm not sure whether we'll be including an additional ruby library but I am planning to implement most of the points suggested in those prototypes directly in C. As I mentioned in my post a moment ago, I've today brought Enumerable into play on Node::Set and XPath and am hoping to get C-side each-xxxx methods on the Node / Attr / etc. before this week's out. I'll admit at this point that I've not deeply studied the additions Mark made in the ruby code, so I may well 180 on this 'not including ruby code' in the near future :-> Cheers, -- Ross Bamford - [EMAIL PROTECTED] _______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
