Why's it inelegant? The parser has to maintain an internal state as it parses the document in addition to on top of the bare state of a new instance. If there were some huge amount of work to be done in creating that new bare instance then it'd probably be worth antagonizing over, but in this particular case the "savings" in "only" throwing away the document state (were some mechanism in the underlying XML::Parser even available to do this in the first place; since it doesn't it's a moot question :) versus just making a new parser instance is more than likely negligible and not worth fretting over.

Update: Gah, tweaked some phrasing and put a phrase back in that got dropped between brane and fingers.

The cake is a lie.
The cake is a lie.
The cake is a lie.

In reply to Re: XML::Checker::Parser - one object, multiple files? by Fletch
in thread XML::Checker::Parser - one object, multiple files? by rekoil

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.