comment on

Thanks. That made me realize my mistake. I was overlooking that caller would return __PACKAGE__."::methodName" not just "methodName".

Yes, it'd be nice if caller offered information about under what name the function was called instead of just under what name the function was compiled.

It'd be nice if the following code:

package Source;
sub orig {
    # use caller() here
}

package Importer;
@ISA= "Parent";
*dest= \&Source::orig;

package main;
Parent->dest();
[download]

Would be able to determine that the caller was trying to find "Parent::dest", found "Importer::dest" via inheritance, and that function which was compiled under the name "Source::orig", rather than only being able to find out that last item.

- tye

In reply to Re^7: Inheritance and calling a subclass method *from* a baseclass method... (rephrase) by tye
in thread Inheritance and calling a subclass method *from* a baseclass method... by EvanK

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks