The easiest way to provide the variable name is with
Data::Dumper::Simple, which uses a source filter. Since the variable name in question is one level higher up the call chain there aren't many options other than
PadWalker, which is usually an indication that you are being a bad person.
Here is an implementation using PadWalker:
use PadWalker qw( peek_my peek_our );
use strict;
use warnings;
sub name(\[$@%&*]) {
for my $pad ( peek_my(1), peek_our(1)) {
while (my ($k,$v) = each %$pad) {
if ($v == $_[0]) {
return $k;
}
}
}
return;
}
our $x = [0];
my @a = (1,2);
my %foo = (1 => 2);
my $subref = sub {};
printf "Name: %s\n", name($x);
printf "Name: %s\n", name(@a);
printf "Name: %s\n", name(%foo);
printf "Name: %s\n", name($subref);
This will work for variables declared with my or our, but not for things like
$::x.
Note that this will not work on older perls that do not support the (\[$@^&*]) style prototype.
-
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.