I'm at home today, with a much slower machine (P166 64Mb, linux 2.2.18pre21, Perl 5.005_03), so I've reduced the number of iterations to a million.
These benchmarks are also with the compl routine checking the length() of the test character first, and with the regex fixed -
Benchmark: timing 1000000 iterations of compl, exist, regex, tr...
compl: 17 wallclock secs (17.35 usr + 0.02 sys = 17.37 CPU)
exist: 15 wallclock secs (14.02 usr + 0.01 sys = 14.03 CPU)
regex: 18 wallclock secs (18.62 usr + 0.00 sys = 18.62 CPU)
tr: 16 wallclock secs (16.67 usr + 0.01 sys = 16.68 CPU)
So, faster than the regex, but still not as fast as the exist() method. Thanks for the suggestion though :-)
Pete
-
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.
|
