Re: Shortcutting a SAX parser
Robin Berjon <[email protected]>
| Newsgroups | gmane.comp.lang.perl.xml |
|---|---|
| Message-ID | <[email protected]> |
On Apr 8, 2009, at 13:34 , Michael Ludwig wrote:
> Robin Berjon schrieb:
>> On Apr 8, 2009, at 11:14 , Michael Ludwig wrote:
>>>> If it doesn't for you, someone must be catching and rethrowing the
>>>> exception and stringifying it along the way.
>>>
>>> Yes, exactly.
>>
>> It would help to know who's doing that, and if it's inside the
>> XML::SAX code (in which case I'm guessing it's a bug). Can you figure
>> it out with Devel::StackTrace or by overriding die() to become
>> confess()?
>
> Here's the output of confess(), which yields no clues to me, but maybe
> to you:
I'm afraid it doesn't clue me in much either, it looks as if it's just
you die()ing in your start_element() and nothing is intercepting it.
The code in XML::SAX::Base doesn't do anything with the exception
unless your method was an AUTOLOAD (which it isn't in your example).
One (tenuous) lead is that start_element is eventually called by
XML::LibXML somewhere up the stack, and that's XS, which on occasion
can lead to surprises. Can you try running the same code with
XML::SAX::PurePerl?
--
Robin Berjon - http://berjon.com/
Feel like hiring me? Go to http://robineko.com/
_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs