Interesting. I was having a similar problem and I solved it by making each of the handlers closures with a shared lexical. While I had each handler as a named subroutine it is also probably better written as a generator. I'll include samples of each mode - what I actually used and what I think is better.

# My actual implementation
{
    my $object;
    sub setobject {
        $object = shift;
    }

    # Each of these routines has access to the shared
    # lexical. Enclosing this whole section in a block
    # prevents the lexical from being used in other scopes
    sub start_handler { ... }
    sub char_handler { ... }
    sub end_handler { ... }
}

# What is probably better though there is a heck of a lot
# of space to move this around. I implemented this as a
# wrapper over some named subroutines and passed the shared
# variable in. You can really do this however you feel.
sub get_handlers {
    my $object;
    return {
      start_handler => sub { start_handler(\@_,\$object) },
      end_handler => sub { end_handler(\@_,\$object) },
      char_handler => sub { char_handler(\@_,\$object) }
    }
}

[download]

Seeking Green geeks in Minnesota

In reply to Re: XML::Parser and objects by diotalevi
in thread XML::Parser and objects by Ineffectual

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.