Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why can't I use a Perl variable's value to access a lexical variable name?

Why does this print 42:

$answer = 42;
$variable = "answer";

print ${$variable} . "\n";

but this doesn't:

my $answer = 42;
my $variable = "answer";

print ${$variable} . "\n";
like image 420
ennuikiller Avatar asked Feb 25 '10 23:02

ennuikiller


2 Answers

Only package variables (the kind declared in your first example) can be targeted via symbolic references. Lexical (my) variables, cannot be, which is why your second example fails.

See the excellent article Coping with Scoping for how the two separate variable systems in Perl operate. And see the also excellent Why it's stupid to use a variable variable name for why that's stupid. :)

like image 200
friedo Avatar answered Nov 08 '22 02:11

friedo


Perl has two entirely separate but largely compatible variable systems, package variables, as in your first example, and lexical variables, as in the second. There are a few things that each can do but the other cant:

Package variables are the only ones that can be:

  1. localized (with local)
  2. used as the target for a symbolic reference (the reason the OP's second example doesnt work)
  3. used as barewords (sub definitions, file handles)
  4. used with typeglobs (because that's what the symbol really is under the hood)

Lexical variables are the only ones that can be closed over (used in a lexical closure).

Using strict would help by forcing you to declare package variables with our, making the difference clearer.

There are several times where symbolic references are useful in Perl, most center around manipulating the symbol table (like writing your own import in a module rather than using Exporter, monkey-patching modules at runtime, various other meta-programming tasks). All of these are advanced topics.

For other tasks, there is usually a better way to do it such as with a hash. The general rule of thumb is to always run under use warnings; use strict; unless you know there isn't any other way but to disable a portion of the pragma (such as using no strict 'refs'; in as small a scope as possible).

like image 33
Eric Strom Avatar answered Nov 08 '22 02:11

Eric Strom