I agree with the comments about the redundant
map. As for readability, I'm a big fan of judicious placement of carriage returns. When it comes to Perl's pipeline idioms, each
map or
grep is another step in the pipeline. That produces code like the following. I've left the redundant
map in to highlight the effect.
return
map { split(/ /, $_, 2) }
map { uc($_) }
@somearray
Sure, if the reader is very new to Perl, they don't understand pipeline idioms at all. However, if the idiom is formatted as consistently as possible, they can absorb it just as quickly as the chaining-return idioms of other languages, like
joe = foo().bar().baz().
--
[ e d @ h a l l e y . c c ]
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.