[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Stopping the SAX parser

• To: "Sterin, Ilya" <Isterin@c...>,<xml-dev@l...>
• Subject: Re: Stopping the SAX parser
• From: "Jeff Rafter" <jeffrafter@d...>
• Date: Sat, 11 May 2002 11:40:40 -0500
• References: <15977008ABB8D5118B1300805FA7A8F10143D4A4@c...>

> One of the most basic facilities of SAX parsers, I'd expect it to allow
the
> parse process to stop and do it's clean up, etc... and proceed with a
> program.  Parsing large docs, once you get the info you need, it's a total
> waste of resources for it to keep parsing the document.

Exactly right.

> I can seem to find in docs or other groups any information on how that
would
> be accomplished.  I mean, yes in some languages you can I guess throw an
> exception and the gargabe collection routine will clean stuff up as needed
> later.  But I'm worried about C/C++ and say Perl/XS combination, where I
can
> kill the parser and catch the exception and continue with my program, but
> the memory will never be cleaned up?

Still throw (or raise) an exception. This should be caught by the parser,
endDocument will be called and then it will be either re-thrown or ignored
(depending on the implementation or exception type). The SAX specs requires
the parser to call endDocument regardless of anything else (for cleanup
purposes expressly). I haven't used the perl modules but in C++ and in
Pascal this is how you should handle it.

HTH,
Jeff Rafter
Defined Systems
http://www.defined.net
XML Development and Developer Web Hosting

• References:
  • Stopping the SAX parser
    • From: "Sterin, Ilya" <Isterin@c...>

• Prev by Date: Re: XPath 2.0 - how much of XQuery should it include?
• Next by Date: Re: frustration (was RE: XPath 2.0 )
• Previous by thread: Stopping the SAX parser
• Next by thread: Re: The vision for XPath 2.0
• Index(es):
  • Date
  • Thread