Hm... Does not seem to be the case.
Perl program actually "dies" - execution ends with the error message on the
standard output. In 0.36, I believe, this happened only if there was no
error handlers provided.
But I will check again.
Thanks.
----- Original Message -----
From: "Kaiserovi" <[EMAIL PROTECTED]>
To: "Sablotron Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 12, 2000 12:01 PM
Subject: Re: [Sab] How to catch exceptions in perl
> Sorry for having overlooked the word "perl" in the subject; my reply is
> related to the C interface. But I think the details aren't much
> different for perl.
> -- Tom
>
> Kaiserovi wrote:
> >
> > It should be pretty much the same... On error, the processing of that
> > particular file stops, nonzero code is returned by SablotRunProcessor()
> > (if that's what you're using) which doesn't prevent you from doing
> > further processing using the same processor instance.
> >
> > Hope this helps,
> >
> > Tom
> >
> > > Nick Semenov wrote:
> > >
> > > The older version (0.36) allowed exception handling, so that one can
> > > provide error handlers also written in perl and continue processing if
> > > such errors would occur. If you process multiple files you do not
> > > want interpreter to bail out on the malformed file - just to catch the
> > > condition and continue.
> > > How this can be achieved in 0.4x?
> > >
> > > Thanks
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
