I thought about using map, but I was mainly illustrating the evolution of the refactoring that I actually did. Plus, the map method isn’t as clear or elegant, at least to my eyes (except for maybe your third example).

And yes, I use a lot of hashrefs for building complex data structures. Hashrefs — they’re what’s for dinner!


{
my ($foo,$bar,$baz) = ('foo val','bar val','baz val');

my @keys = qw/foo bar baz/;
my @values = ($foo,$bar,$baz);

# You can use map like the foreach
my %hash = map { $keys[$_] => $values[$_] } 0 .. $#keys;
my %hash = map { $keys[$_] => shift @values } 0 .. $#keys;
my %hash = map { $_ => shift @values } @keys;
my %hash = map { $_ => shift @values } qw/foo bar baz/;

# I tend to use hashrefs for passing stuff around
my $hash = {'foo'=>$foo,'bar'=>$bar,'baz'=>$baz};
print $hash->{'foo'};

# Plus with hashrefs you can make them really complex and
# still return them from a sub

}


However, I have been kicking around some ideas for a post about OOP zealotry…