This actually seems to be slightly quicker than the grep based solution: Benchmark: timing 100000 iterations of broquaint, grep_seen, aristotle
+, juerd...
broquaint: 25 wallclock secs (21.62 usr + 0.01 sys = 21.63 CPU) @ 46
+22.99/s (n=100000)
grep_seen: 12 wallclock secs (11.55 usr + 0.00 sys = 11.55 CPU) @ 86
+60.26/s (n=100000)
aristotle: 10 wallclock secs ( 9.05 usr + 0.00 sys = 9.05 CPU) @ 11
+044.84/s (n=100000)
juerd: 9 wallclock secs ( 8.66 usr + 0.00 sys = 8.66 CPU) @ 11
+543.35/s (n=100000)
on my @list = qw/a b c d d a e b a b d e f a erti wen udfgn
wei sdej usdjdh iu t k a b b b b a a a a c d f e f s r s
gkl h u s y t d s w s d log u log ds/;
Jenda
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
Edit by castaway: Closed small tag in signature
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|