Thanks for the reference. I think I must have been away that day cos I do not remember that thread at all. And looking at my posting history, I didn't post anything that entire week.
With regard to \&{ $coderef } versus \&$coderef: I discovered long ago that
- there is no performance difference between sigil{ $scalar } & sigil$scalar;
- and that (for example) print for @{ $_[0] } works, where print for @$_[0] doesn't.
Hence, the 2-char longer (4 if you count my preferred whitespacing) form has no downsides and benefits from the extra clarity when the scalar being dereferenced comes from a compound source. Plus I do not have to try and remember when I have to use the longer form and when I can get away with the shorter. And I like consistency.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
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.