It looks like you'd still have to do some processing in your class's new().
If you look at HTML::Parser::new(), it calls HTML::Parser::init() to
actually install the pieces it needs.
In your new(), you'd have something like:
my $self = bless {}, $class;
# some stuff
$self->init(@_);
# more stuff
This will add the hash elements to your class object that HTML::Parser needs
and will parse any options it knows how to handle. This assumes that your
class is subclassed from HTML::Parser and neither your class nor any of the
other parent classes that appear earlier in @YourClass::ISA (if any) have an
init() method.
This is all my best guess. I'll have to send a documentation patch to Gisle
and see if my guess is what he intended.
--
Mac :})
----- Original Message -----
From: "KIMURA Takeshi" <[EMAIL PROTECTED]>
To: "Michael A. Chase" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, April 12, 2000 5:18 PM
Subject: Re: HTML::Parse overwriting sub parse
> Michael A. Chase wrote on 00.4.12 4:45 AM:
> >HTML-Tree had similar problems. Look in HTML::TreeBuilder->new() to see
how
> >he worked around it. The archive on CPAN is HTML-Tree-0.65.tar.gz.
>
> Does this mean that I have to over-ride new()?
>
> I also found in the list archive that in case of HTML-Tree, the
> problem was fixed by adding an initializer to HTML::Parser or HTML::
> Element to allow one to initialize objects of the other's class.
>
> Am I getting to the point?
