Actually, i disagree on the point of keeping the arrows in. Since everything after the first level is always a reference, the extra arrows are just line noise. It's just as easy to remember never to put them, rather than always to.
Also, that frees you up to concentrate on the real issue of whether your top level access is by reference or not.
So all the -> rules essentially (for simple to moderate cases) boil down to ref = -> at the top, hash (or list, etc) = no ->
And as a side note to another point you made, I have started following Damian's advice about the deref and have been writing:
%{$hashref}
instead of:
%$hashref
it seems a little more readable, especially with a little whitespace:
%{ $hashref }
-pete
"Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere."
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.