I could see one or two valid uses. The one place I've used it for production was a tied hash package. We wanted to be able to alias package vars in the hash values with vars from the caller. Retrofitting this to older code was a pain as they HAD to be package variables so we changed the alias sub to look at caller's lexicals and then the package vars.
-Lee
"To be civilized is to deny one's nature."
Update
While on the subject, I should mention a bug/feature of PadWalker. It will NOT see all lexicals visable where the subroutine is called if you have a bare block
#!/usr/bin/perl -w
use strict;
use PadWalker qw(peek_my);
my ($oa,$ob) = ("Outer One", "Outer Two");
{
my $inb = "Bare Block"; # Will not be seen by peek_my
peeper();
}
sub peeper {
my $c = peek_my(1);
print "Lexicals:\n", (map { "Found $_ with value $c->{$_}\n" } sor
+t keys %$c ),"\n";
}
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.