I changed this around to do it for arbitrary coderefs, since I get to deal with some that come from other sources. Instead of catching them at definition time, I "enchant" them later.
This looks like it could be a useful decorator if I work on the concept a little more. So Randal, who wants to upload it to CPAN first?
#!/usr/bin/perl
my $a = sub { print "I am A\n" };
my $b = sub { print "I am B\n" };
$a->();
$b->();
$c = MagicalCodeRef->enchant( $a );
$a->();
print STDERR "That was $a I just called\n";
BEGIN {
package MagicalCodeRef;
use overload '""' => sub
{
require B;
my $ref = shift;
my $gv = B::svref_2object($ref)->GV;
sprintf "%s:%d", $gv->FILE, $gv->LINE;
};
sub enchant { bless $_[1], $_[0] }
}
--
brian d foy <bdfoy@cpan.org>
-
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.
|