It's more than a message; it's a fatal error.

If you run it under diagnostics:

Uncaught exception from user code: calling depth after parsing is finished at /opt/perl-5.8.6/lib +/site_perl/5.8.6/i686-linux/XML/Parser/Expat.pm line 474 at /opt/perl-5.8.6/lib/site_perl/5.8.6/i686-linux/XML/Parser.pm line +192 XML::Parser::parse('XML::Twig=HASH(0x81ec750)', '<node id="17" +><content>foo bar</content><child file="19.xml" ...') called at 48649 +7.pl line 9

Frankly, I would not expect the parser to brook such treatment. Why not create a new parser in onChild?:

sub onChild { my ($t, $child) = @_; my $atts = $child->atts; XML::Twig->new( twig_handlers => { child => \&onChild } ) ->parsefile($atts->{file}); }

the lowliest monk


In reply to Re: Recursion and XML::Twig by tlm
in thread Recursion and XML::Twig by BioHazard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.