I have to weigh in against the "silently modify the arguments"
approach. Of course good (and very LOUD) documentation can
offset most of the danger, but most people don't expect to
have arguments modified by a subroutine.
IM(ns)HO, the occasional '\' is a very small price to pay
for self-documenting code. If it strikes you as jarring, I
think that is all the more reason to use it. You (and the
one who maintains your code) will instantly recognize an
atypical behavior when you see an unusual syntax in use.
I don't think the @_ trick is evil. There is a time and place
to use it, just like the &func construct (re-using the current
@_), but it should only be used judiciously.
Russ
Brainbench 'Most Valuable Professional' for Perl
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.