[Expat-discuss] Exiting expat handlers
Thu, 17 Oct 2002 13:29:02 +0300
This is a multi-part message in MIME format.
---------------------- multipart/alternative attachment
I see your point here. I just found out that i can use: void XMLPARSEAPI =
XML_UseParserAsHandlerArg(XML_Parser parser); expat API. Or simply pass =
my parser instance as a parameter to the userdata member of callbacks. I =
am using the C library of expat.
Now, if an error occurs, i can just call =
XML_FreeParser(myparserinstance); safely inside my handler procedure? I =
am using a C++ wrapper class for the C expat APIs.
----- Original Message -----=20
From: "Warren Crossing" <email@example.com>
To: "Firas Abughazaleh" <firstname.lastname@example.org>; =
Sent: Thursday, October 17, 2002 1:00 PM
Subject: RE: [Expat-discuss] Exiting expat handlers
> The first parameter of the callback sub is a reference to the parser!?
> When you encounter an application specific error can you call =
> and/or finish() ?
> are you using lib expat for perl or c?
> > -----Original Message-----
> > From: Firas Abughazaleh [SMTP:email@example.com]
> > Sent: Thursday, October 17, 2002 10:47 AM
> > To: firstname.lastname@example.org
> > Subject: [Expat-discuss] Exiting expat handlers
> > Hi all,
> > Anyone knows how can you exit an instance of expat gracefully if you =
> > inside an element handler and you encountered an error inside it?
> > Thanks,
> > - Firas
> This message is intended only for the addressee and may=20
> contain information that is confidential or privileged.=20
> Unauthorised use is strictly prohibited and may be unlawful.
> If you are not the addressee, you should not read, copy,=20
> disclose or otherwise use this message, except for the
> purpose of delivery to the addressee. If you have received
> this in error, please delete and advise us immediately.
> Although Company Watch makes every reasonable effort to keep
> its network and systems free from viruses, the company
> accepts no responsibility for computer viruses transmitted
> through this mail or in any attachments. It is your
> responsibility to virus scan any attachments we send to you.
---------------------- multipart/alternative attachment--