This is all good, but I would say that "end weight" should
be the deciding factor. In this case (and probably in most
cases), the source of the list is very simple (just an array)
so it makes more sense to specify the list first, and then
follow it with the block of code acting on it: you use
foreach.
In cases where the source of the list you're acting on is
more complicated, you might be able to improve clarity by
switching this around and using map to put the code block
first, followed by the list.
(By the way, did you know that map has now been optimized
for use in void context? It used to be you'd take a performance hit for using map instead of foreach, but that's
not true anymore, for the latest versions of 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.