Apologies if this has already been raised - I did look in SuperSearch.
Strange behaviour (bug?) of use strict 'subs' (was: ... strict 'vars') dances around it.
Documentation for
strict 'subs' states:
... generating a compile-time error if you try to use a bareword identifier that's not a subroutine, unless it ... appears in curly braces...This does not appear to be the case for keys in a hash slice. For example:
use warnings;
use strict 'subs';
my %hash = qw (k1 v1 k2 v2 k3 v3);
$hash{k1} = 42; # is fine
@hash{k1,k2,k3} = (1,2,3); # BANG! Bareword "k1" not allowed...
@hash{qw(k1 k2 k3)} = (1,2,3); # is fine
(Windows ActiveState 5.10.1)
Why are single keys and multiple keys handled differently?
OK, so a hash slice uses a list instead of a scalar, but why should that make a difference? Is an unquoted list somehow more dangerous than an unquoted scalar value?
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.