I was shocked to read that, till ...
DB<24> $h{length}=3 => 3 DB<25> \%h => { length => 3 }
... I realized the behaviour is sane (autoquoting of barewords) and that you want it reversed to DWIM magic which is easily avoided with little explicit syntax.
just use parens if you really want to avoid an explicit $_
DB<33> $_="abc" => "abc" DB<34> $h{length()}=42 => 42 DB<35> \%h => { 3 => 42, length => 3 } DB<36> $_="abcd" => "abcd" DB<37> $h{(length)}=666 => 666 DB<38> \%h => { 3 => 42, 4 => 666, length => 3 }
In this contrived case ( length as a hashkey? ) I'd personally reject anything other than
DB<39> $h{length $_}= 'best' => "best" DB<40> \%h => { 3 => 42, 4 => "best", length => 3 }
in code review.
Question Are you possibly unconciously trolling???
Opinion I doubt that ... but keep on trying to entertain us.
Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
In reply to Re: Opinion: where Perl5 wasn't attractive for me
by LanX
in thread Opinion: where Perl5 wasn't attractive for me
by rsFalse
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |