In one of the XSLT tests for the reworked libraries, the XML parser is
reading data from some location other than scanner.input_stream. I
know this is the case, because I recognize some of the content text -
this comes from a previous data XML file, processed in a previous step
of the test. The first step generates a transformation in-memory,
according to the contents of this data file. The second step uses
this generated transformation to process yet another data file.
It is while compiling the generated transformation that the bad
content appears. The whole of the generated transformation is
correctly parsed, but the parsed xsl:stylesheet element has 6 children
instead of 5, and the fifth child is a text node with this errant
data.
What I would like to know is where the scanner can read it's input
other than from `input_stream', so I can debug this better.
--
Colin Adams
Preston Lancashire
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
gobo-eiffel-develop mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
