Having done some tests, and it also seems to make perfect sense to me... the 2nd version,
my @slice=@{$href}{'item1','item2'};
Is the only one which seems valid for the purpose at hand. The target is to get a hash slice, which is array (ahem, list) context, so
@{$href} is what places it in that context, dereferencing as an array, to mimic
@hash{'item1','item2'}
${$href} on the other hand attempts to dereference as a scalar, which, in my test, didn't yeild anything but undef:
#!/usr/local/bin/perl
use strict;
my %hash = map { chr(ord('@')+$_) => $_ } (1..26);
my $hashref = \%hash;
my @list = qw/A B L S Z/;
my @slice = @{$hashref}{@list};
my $multi = ${$hashref}{@list};
print '@slice == ['. join(', ', @slice). "]\n";
print "\$multi == '$multi'\n" if defined $multi;
print "\$multi == undef\n" if !defined $multi;
Output:
@slice == [1, 2, 12, 19, 26]
$multi == undef
So it seems only one of these gets the desired result, and thus no ambiguity.
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.