I guess the error comes from your class MUCParser, possibly in the subroutine num_of_tags, because HTML::Parser works for me independently. But HTML::Parser itself does not store any state, especially not anything like a tag count, so it is mostly interesting what your num_of_tags subroutine does and how/where it stores the tag count. If for example your MUCParser class looks like the following:

package MUCParser;
use strict;
use base 'HTML::Parser';

use vars '$tag_count';

sub new {
    my ($class,@args) = @_;
    ...
    my $self = $class->SUPER::new(@args);
};

sub num_of_tags {
    return $tag_count;
};

[download]

then, $tag_count is a global variable and all your MUCParser instances will share that variable. Some more information, like the (stripped down, relevant) source code of MUCParser is needed.

In reply to Re: Parsers overwriting each other by Corion
in thread Parsers overwriting each other by bwgoudey

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.