NEXT doesn't like this because it uses
caller to find the calling package, and
caller sees the package the function was compiled in, not the one that was called.
You have the right idea with the eval approach, but I was suggesting something more like this:
sub import {
my $package = shift;
my $methodname = shift;
my $dest = caller;
my $compiled_in = __PACKAGE__;
# The initial comment improves error messages.
eval qq{# line 1 "Loaded by $compiled_in\::import"
package $package;
sub $methodname {
return shift->SUPER::blah();
}
};
die $@ if $@;
}
Also note that your imported symbol
can make use of closure variables without interpolating them. If you put \$foo in your code, that will be compiled as $foo, and that will pick up any lexical $foo that is in scope when the
eval happens.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.