My preference is to do the space trimming in two stages as it seems to be faster than either the capture or alternation methods.
use strict;
use warnings;
use Benchmark q{cmpthese};
my @arr = ( q{ fdsgehw fw wwfe w } ) x 5000;
cmpthese(
-5,
{
alternation => sub
{
my @new = @arr;
s{ ^\s* | \s*$ }{}gx for @new;
},
capture => sub
{
my @new = @arr;
s{ ^\s* (\S.*?) \s*$ }{$1}x for @new;
},
twoStage => sub
{
my @new = @arr;
s{ ^\s* }{}x for @new;
s{ \s*$ }{}x for @new;
},
},
);
The results.
Rate capture alternation twoStage
capture 8.96/s -- -26% -50%
alternation 12.2/s 36% -- -33%
twoStage 18.1/s 102% 48% --
I hope this is of interest.
Cheers,
JohnGG
Update: Fixed code indentation problems caused by TABs
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.