Hi, Has there been a discussion about the memory-model changes? If so, I am interested to understand the direction better. Is there a particular list thread that I might read?
In my past ruby extensions I have avoided giving the GC any more than necessary, to limit memory copying as well as performance. Is the libXML memory model unstable to keep pointer references to? Dan On Jun 9, 2006, at 13:54, Ross Bamford wrote: > On Fri, 09 Jun 2006 17:36:16 +0100, Dan Janowski <[EMAIL PROTECTED]> > wrote: > >> Hi, >> >> I have just started using libxml2 for ruby and have come to a >> problem. Attribute traversal is broken. Only the first attr is >> accessible from .properties. >> > > This one is on my list to look at, so thanks for the patch :) This > issue > is actually connected to the memory management problems I'm working > on at > the moment, and I'm going to be making a few changes to the way we > share > libxml2 data between ruby instances, since this is currently causing > problems, especially when multiple documents are involved. > > What I'm aiming for is to let ruby's GC handle as much of the > management > as possible, which will probably mean copying things around a bit > in some > cases (e.g. copying between documents), but I think in this case we > could > use xmlCopyPropList instead of xmlCopyProp to take care of that. > > Anyway, I'll integrate this fix into my changes and will hopefully be > committing very soon. I've taken the liberty of filing a bug report > for > this in the meantime. > > Thanks, > -- > Ross Bamford - [EMAIL PROTECTED] > _______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
