[ expat-Bugs-850946 ] Way for handler to report parse errror
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.text.xml.expat.bugs |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #850946, was opened at 2003-11-28 18:19 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=850946&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Way for handler to report parse errror Initial Comment: There also appears to be no way for a content handler to return an failure case back to expat. Just because the xml is well formatted, does not mean that the data inside is. All of the handler calls just return void, and call the next routine. If exceptions are expected to be used, then make sure that path is exception safe. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-11-28 18:31 Message: Logged In: YES user_id=290026 Expat concerns itself with well-formedness only. However, if you wish to abort parsing for any reason, there are several ways to terminate: - use exceptions (this works for me) - use setjmp/longjmp - use the new feature XML_StopParser() which you have to call from a handler. The third feature is currently available as patch #835123 only, but should make it into one of the next releases in some form or another. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=850946&group_id=10127