Thanks Tom.
Yeah for XML::Parser line 236 perhaps we can get Clark (Current maintainer
according to POD) to change it to
return undef if $err;
Mark.
ps: I'll check that rule (tommorow. ..must...have...sleep..)
Tom Harper wrote:
> Mark--
>
> While you may be having problems with segfaults because
> of expat = yes rule-- i was having similar problems
> with XML parser relating to the the die statement.
>
> I do the same thing as far as eval'ing the parsefile
> call. Also, I removed the die statement from parser.pm
> (v 2.29 line 240 or so) so it would return a useful error
> message rather than just die uninformatively.
>
> Maybe this is what you were asking about?
>
> Tom
>
> At 09:19 AM 5/4/01 +0100, Matt Sergeant wrote:
> >On Fri, 4 May 2001, Perrin Harkins wrote:
> >
> >> on 5/4/01 9:28 AM, Mark Maunder at [EMAIL PROTECTED] wrote:
> >> > I have an Apache::Registry script that is using XML::Parser. The
> parser throws
> >> > a
> >> > 'die' call if it encounters a parse error (Why?).
> >>
> >> Because it's an exception and the parser can't continue.
> >>
> >> > I was handling this by
> >> > putting
> >> > the code in an eval block, but this no longer works since all Registry
> scripts
> >> > are already in one huge eval block.
> >>
> >> It should still work. An eval{} is scoped like any other block. Maybe you
> >> have a typo? Post your code and we'll look at it.
> >
> >More likely is a b0rked $SIG{__DIE__} handler, like fatalsToBrowser. Yick.
> >
> >--
> ><Matt/>
> >
> > /|| ** Founder and CTO ** ** http://axkit.com/ **
> > //|| ** AxKit.com Ltd ** ** XML Application Serving **
> > // || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
> > // \\| // ** mod_perl news and resources: http://take23.org **
> > \\//
> > //\\
> > // \\
> >
--
Mark Maunder
[EMAIL PROTECTED]
http://swiftcamel.com/
Try not.
Do.
Or do not.
There is no try.
~yoda
