The advantage of limited over unlimited split is more pronounced if a redundant subroutine call and lexical creation are not included, with regex extraction thrown in for good measure:
c:\@Work\Perl>perl -wMstrict -le
"use Benchmark qw/cmpthese/;
;;
my $string = '1:13:1:6:5854:0x00E37F06:0x00D1314C';
my $result;
;;
sub _split {
$result = join ':', (split /:/, $string)[0 .. 2];
}
;;
sub _split_LIMIT {
$result = join ':', (split /:/, $string, 4)[0 .. 2];
}
;;
sub _regex {
($result) = $string =~ m{ \A \d+ : \d+ : \d+ }xmsg;
}
;;
cmpthese(-5, {
_split => \&_split,
_split_LIMIT => \&_split_LIMIT,
_regex => \&_regex,
});
"
Rate _split _split_LIMIT _regex
_split 261407/s -- -39% -54%
_split_LIMIT 425387/s 63% -- -24%
_regex 562521/s 115% 32% --
-
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.
|