Re: AW: AW: HowTo find out all schema validation errors, not only the first?

[keshlam]

There are very few parsers, for any language, which can "report all errors" reliably. Hitting a parse error often makes determining whether later code is correct very difficult. It's possible to write parsers which attempt to recover and continue, but there are generally performance costs in doing so and even those can't promise that they'll find everything since how you resolve one error in the file may determine whether a later issue is a mistake or not.

Given the performance issue, I'd suggest that an "all errors" parser might want to be a separate project, so Xerces itself can stay as fast as possible. At the very least, it should be a separate mode which has zero performance cost when not selected.

______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html)