comment on

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;
          },
   },
   );
[download]

The results.

              Rate     capture alternation    twoStage
capture     8.96/s          --        -26%        -50%
alternation 12.2/s         36%          --        -33%
twoStage    18.1/s        102%         48%          --
[download]

I hope this is of interest.

Cheers,

JohnGG

Update: Fixed code indentation problems caused by TABs

In reply to Re: Trimming whitespaces methods by johngg
in thread Trimming whitespaces methods by harishnuti

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.


The stupid question is the question not asked
	PerlMonks