Your test for a "bad pointer" in Element::copyData() looks
strange to me, but there's definately something weird going
on. I'll add it to my plate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tried this again using the CVS version of Expat and
the test for a "bad pointer" disabled, and saw no ill
effects. Please test with the CVS version of Expat if
possible. Be sure to follow the instructions in the README
to build the XML_UNICODE version of the library.
I'll ignore this until you're able to confirm that there's
still a problem in a more current version of Expat (with a
strong preference for the CVS version).
Following up to this report on SourceForge will add this
back to my list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I noticed also that depending on the size of the
buffer the parser is using, the CharacterDataHandler routine
is given just a portion of the data between the start and
end tags because it is split across two buffers of xml from
the stream (a file in my case). This causes the
CharacterDataHandler to then be called again with the
remainder of the text data. Shouldn't expat put the two or
more pieces together as one string and then call the handler?
Respectfully,
Bill Lynn
blynn@jtls.nps.navy.mil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Simple test case shows problem
Logged In: YES
user_id=3066
Your test for a "bad pointer" in Element::copyData() looks
strange to me, but there's definately something weird going
on. I'll add it to my plate.
Logged In: YES
user_id=3066
I just tried this again using the CVS version of Expat and
the test for a "bad pointer" disabled, and saw no ill
effects. Please test with the CVS version of Expat if
possible. Be sure to follow the instructions in the README
to build the XML_UNICODE version of the library.
I'll ignore this until you're able to confirm that there's
still a problem in a more current version of Expat (with a
strong preference for the CVS version).
Following up to this report on SourceForge will add this
back to my list.
Logged In: NO
Well, I noticed also that depending on the size of the
buffer the parser is using, the CharacterDataHandler routine
is given just a portion of the data between the start and
end tags because it is split across two buffers of xml from
the stream (a file in my case). This causes the
CharacterDataHandler to then be called again with the
remainder of the text data. Shouldn't expat put the two or
more pieces together as one string and then call the handler?
Respectfully,
Bill Lynn
blynn@jtls.nps.navy.mil