I think it falls on the programmer's shoulders
to make sure her code does not expect that the
function isn't going to mangle
$_. There are just
too many places that
$_ could get screwed up.
Besides, I like to explicitly define what the item is that
I'm dealing with. I find it much more sane to say, for
example:
for my $isbn ( @isbns ) {
dosomething($isbn);
than just implicitly saying
for ( @isbns ) {
dosomething($_);
Besides, in the latter case, you have to ask yourself a
question: "Where is the $_ coming from, and what is it?"
It should be every programmer's job to eliminate any
such potential questions from the minds of future maintainers,
even if it's herself.
Can you tell I'm working on my departmental coding standards? :-)
xoxo,
Andy
%_=split/;/,".;;n;u;e;ot;t;her;c; ". # Andy Lester
'Perl ;@; a;a;j;m;er;y;t;p;n;d;s;o;'. # http://petdance.com
"hack";print map delete$_{$_},split//,q< andy@petdance.com >
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.