Seeing that no one else has responded, I take as my cue to raise a red
flag. I haven't talked to Dan about this, but I'm going to go out on a
limb and say, that after following this project for many years now --
not to mention personally working to revitalize it TWICE, I've come to
the conclusion t
On 3/5/08 7:19 AM, Trans wrote:
> While problems could be arising from libXML2 itself I suspect that it
> is not generally the case, which makes me wonder how libxml-ruby is
> actually designed under the hood.
Just for the record, I've never had these problems with the Python libxml2
binding 'l
Trans,
Thanks for replying. Although your answer doesn't help solve my
problem with libxml-ruby it does give me a sense that it's going to
take long to get this fixed.
At least I can start rewriting my schemas in Relax NG now, so that I
can meet my application production rollout deadline.
Saurab
> 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 wor
As someone who has experienced a good number of these crashes, who has
attempted to track them down, and who has at least some C experience, I
would like to make a recommendation.
From my own reading and limited understanding of the code I don't think
there is anything fundamentally wrong. At lea
