I also found a bunch of similar leaks, plus one different kind which was
leaking on every xpath find. I communicated once with Dan Janowski and sent
him this set of patches, then never heard back from him again, so not sure what
happened. Here are the leaks I fixed, if you have others, please
When you posted that you had applied the patch, I updated and nothing came down
so I was confused. I see that you have been very busy, awesome! Anyway, some
of those patches that I just sent are still applicable.
Should it be possible to build the gem on Windows with VC6 with what's checked
i
Hi Tom,
Tom Bagby wrote:
When you posted that you had applied the patch, I updated and nothing came down
so I was confused. I see that you have been very busy, awesome! Anyway, some
of those patches that I just sent are still applicable.
SVN is updated but I haven't wrapped up a new gem ye
Hi Tom,
I also found a bunch of similar leaks, plus one different kind which was
leaking on every xpath find. I communicated once with Dan Janowski and sent
him this set of patches, then never heard back from him again, so not sure what
happened. Here are the leaks I fixed, if you have othe
I also found a bunch of similar leaks, plus one different kind
which was leaking on every xpath find. I communicated once with
Dan Janowski and sent him this set of patches, then never heard
back from him again, so not sure what happened. Here are the leaks
I fixed, if you have others, pl
libxml-devel@rubyforge.org
Hi everyone,
As you might have guessed by the recent email traffic, I've dived into
the libxml (and libxslt) ruby bindings since I need them MapBuzz.
Thanks to Sean for developing the bindings and Dan for reworking the
memory model. From what I can tell, the libra
