in reply to Creating stub methods

A more traditional practice is to provide "stub" subroutine declarations:
sub foo; sub bar;
At the moment, I can't remember exactly what problem this solves, but it should make them show up in can now. If you could figure out how this affects the symbol table and simulate that with your code (rather than a goto &AUTOLOAD), you might be closer to useful.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Replies are listed 'Best First'.
Re: •Re: Creating stub methods
by Anonymous Monk on Dec 29, 2003 at 18:18 UTC
    At the moment, I can't remember exactly what problem this solves
    It solves the prototyping problem (%s() called too early to check prototype ).

        It solves the problem of method look-up by-passing your module and continuing up the inheritance tree.