While your point is flawlessly made, I'm curious about one thing: Did you go back and re-run the program using split? If the file gets cached, you may be seeing artificial improvements. This is where the BenchMark.pm module can really help in a comparison like this.
Without seeing your data, I imagine you'd take one line that matched your criteria, and one that didn't. Then write a comparison using both a passing and failing case with your data, duplicated to use split one way, and the regexp the other. This eliminates the file system as a possible source of artificial improvements.
There was a dicussion about whether split was faster than a regexp or not, rather recently. I don't recall the outcome, but that node may be worth hunting up.
--Chris
e-mail jcwren
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.