I'm going to have to agree with holli on this and say Why not just use the hash? If you must do something like this, know that it is in violation of some of the tenets of strict. Here's a version with limited un-strict-ness that does not use an eval:

#!/usr/bin/perl -l

use strict;
use warnings;

my %foo = (
    _foo => 'FOO',
    _bar => 'BAR',
    _baz => 'BAZ',
    zum  => 'ZUM',     # do not make this one a "real" variable
);  

{   # limit the scope of the following 'no strict' 
    no strict 'refs';

    # There be magic here!  This will get the keys from %foo
    # then attempt to remove the leading '_'.  If it works, 
    # the *modified* key gets passed along; otherwise, the
    # key is stripped from your processing list.  We then
    # dynamically create a variable with the name of the
    # modified key and assign it the value of the unmodified
    # key in the hash.
    $$_ = $foo{"_$_"} for (grep { s/^_(.*)/$1/ } keys %foo);
}   

# this is so we can speak the variable's name without Perl throwing a 
+fit
no strict 'vars';
print for ($foo, $bar, $baz, $zum);  # should produce one 'unitialized
+' warning
[download]

I don't agree that this is good practice. However, do what you must to get the task accomplished. I know too well what it is to maintain ugly code, even when the original author was me.

---

---

• 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.