Perl-Sensitive Sunglasses | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
There may be good reason to qualify the seemingly redundant use of the arrow dereferencer between the deepest subscripts. If not solely to understand what is happening in a different way. ...is the same as
The manner in which dereferencing occurs is different but the result is the same. Most feel the arrow manner is simpler on the brain, being more intuitive once you have grasped the notion of dereferencing. lets reduce the complexity for a moment
we can now reach the first level reference to the array and by all accounts either syntax is fairly comprehensible. Lets increase the complexity back up.
You can already see the way of the arrow is clearer as the start of the dereference does not accumulate the scalar sigil for each depth of level of complexity. And to be fair this starts literally looking subsequently more expensive too. The toppler of the cake is that the arrow way also adds the optimisation of saying, hey you know what, seeing as we're already dereferencing here lets not bother making a christmas decoration out of the expression and voila! you get...
Making the array actual, you use dereffing where its needed, not between the first level subscript but between the second level subscript.
Comparing the position of the arrow between $VAR3 and $VAR4[0], it would seem this gives us a qualifier for telling us when in a complex structure a 'reference to' or 'an actual' hash/array resides at the first level. The reason being data structures only hold scalars. The very reason for the requirement of referencing. As a reference to a complex structure is a scalar. And this of course means the arrow way can safely bah humbug the merry season with all the capacity of your ram. my $ah={h=>'a'};print %$ah for 0..2; In reply to Re^3: problem with array of hashes
by Don Coyote
|
|