Well, I think I've been successful in changing the Xerces code to prevent this. Running my program, within or without an attached debugger, now takes about the same time (90,000 monitored exceptions can slow things down quite a bit). However, I don't know what's involved in issuing an official change to a package like Xerces, you know, licenses, fine prints, "liars", et al.. But when I have some time I'll check to see if it can be done.
Thx, d. Boris Kolpackov-2 wrote: > > Hi, > > Friponneau <[email protected]> writes: > >> So, I'm wondering if there's a way of preventing those exceptions to be >> thrown by overriding something somewhere in xerces. > > I don't think this is possible. It is pretty bad that we throw exceptions > during normal execution of the parser. If you would like to come up with > a patch that fixes this, then that would be great. > > Boris > > -- > Boris Kolpackov, Code Synthesis > http://codesynthesis.com/~boris/blog > Compiler-based ORM system for C++ > http://codesynthesis.com/products/odb > Open-source XML data binding for C++ > http://codesynthesis.com/products/xsd > XML data binding for embedded systems > http://codesynthesis.com/products/xsde > > -- View this message in context: http://old.nabble.com/EndOfEntityException---Performance-in-DEBUG-tp29956646p29966300.html Sent from the Xerces - C - Users mailing list archive at Nabble.com.
