On Mar 7, 5:47 am, Dan <[EMAIL PROTECTED]> wrote: > Hi, > > Sorry I have been off the radar, some personal crap has been keeping me > occupied. > > The memory model changes have been largely effective and creates a good > one to one coupling between ruby object and libxml entities. The issue > that sean is talking about is no longer the case. I have removed > Reference counting everywhere I have been and multiple recall of an > entity will return the same ruby object. I do not believe the libxml2 > library is at all the problem. My greatest frustration has been the the > GC and debugging and memory tracking. Basically the GC sucks and the > way it is written and that it lacks any instrumentation for debugging > makes for nothing but trouble. I have worked with Marc directly on a > number of faults and have been largely successful, but the time cost is > high, and I cannot make this my life's work. > > There are components that have not been evaled or rewritten yet and the > problems that people are be experiencing may be the result of mixing > those features. May or may not, since I have not looked. > > I have contemplated abandoning support, but I would rather not. Being > the only coder makes it harder as ultimately every bug is my problem. > But that is not the issue, ruby 1.8 is. I have considered moving to > rubinius to see if their compatibilty api is better than the original. > But that may yield nothing as it could work fine there. 1.9 I have not > considered, but valgrind is sort of a white elephant since the GC > screws things up without a trace before the real problem occurs. > > I am open to suggestions, but I can't do this part on my own.
Hey Dan, what do you think of forwarding this to ruby-core mailing list? I'm suspect the best input on the matter might come from there. T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
