This is exactly why I personally avoid attributes. That's a kind of code fragility that I don't like. Particularly since I like using
Apache::Reload. If there is an alternate solution, I'm interested to hear it. But I just avoid using attributes.
In your case I might do something like this in the parent class (untested):
sub wrap_sub {
my ($class, $function) = @_;
no strict 'refs';
no warnings 'redefine';
my $referent = \&{"$class\::$function"};
my $wrap_sub = sub {
warn 'before';
$referent->( @_ );
warn 'after';
};
warn "wrap_sub wrapping: $class\::$function";
no warnings 'redefine';
*{"$class\::$function"} = $wrap_sub;
return;
}
And then in your child class you write:
sub foo {
warn 'fooooo';
}
__PACKAGE_->wrap_sub("foo");
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.