While demonstrating one point is wrong (and again making it
clear that until you benchmark, you don't really know what
is faster), you demonstrate the other.
What happens in your chunk code with the last line? Which
is more code? And when you are doing fixing that you may
still be twice as fast but with quite a bit more (and
harder to read) code. Going forward that is more to
maintain.
I would strongly argue against this optimization (which
I think might well give different results on different
operating systems) until after your system is built and
performance is known to be a problem.
One note though. The IO* modules generally have
significant overhead and I don't recommend using them.
EDIT
Another bug. You used split in the chunk
method without the third argument. Should your block land
at the start of a paragraph, you would incorrectly lose
lines!
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.