I preach about separation of presentation and content
when i discuss CGI scripts, but i unintentionally strayed
from that principle with this subroutine:
sub trim {
return map { s/\.mp3\z/\n/; $_ } sort @_;
}
How? By 'decorating' each filename in the list with a
newline. Oops!
Better would be the following:
sub trim {
return map { s/\.mp3\z//; $_ } sort @_;
}
# and decorate it in the 'client'
print DB map {"$_\n"} trim(@files);
Of course, the downside is two maps instead of one, but,
this is better when making generic, robust, reusable
subroutines. Allowing the client to make this decision
could very well cut back on the number of modifications
required for that subroutine.
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
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.