> Seeing that no one else has responded I don't know if it's been nixed or not, but the is_shadow concept is fundamentally broken in any sophisticated workload. Every operation needs to return a copy. I initially did the shadow bits for speed reasons (object thrash), which satisfied my workload requirements at the time, but it's proven to be a really bad idea in practice. If I had cycles/interest in rewriting things, I'd take aim at anything that returns a wrapped xml object and would return a copy of the object instead. What I believe is happening is the GC is coming along, invalidating portions of the XML document structure, and leaves a dangling pointer. I don't know if that's what Dan fixed in the latest rev or not, but that's the only design thing that I'm aware of that _needs_ to get addressed. Is this still feasible? -sc
-- Sean Chittenden [EMAIL PROTECTED] http://sean.chittenden.org/ _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
