comment on

While I agree about the benchmark result, I don't agree with what you call "Skeeve's". Try this:

use Benchmark 'cmpthese';

our @data = ('foo', 'foo bar', ' foo', 'foo  ', ' foo ', ' foo bar ');
+ 

cmpthese -1, {
  faq    => 'my @f= map {local $_ = $_; s/^\s+//; s/\s+$//; $_ } @::da
+ta',
  Skeeve => 'my @f= map { /^\s*(\S.*?)\s*$/ && $1 || "" } @::data',
  ikegami => 'my @f= map { /^\s*(.*?)\s*$/; $1; } @::data'

}; 
__END__
           Rate  Skeeve ikegami     faq
Skeeve  24561/s      --     -8%    -28%
ikegami 26614/s      8%      --    -22%
faq     33998/s     38%     28%      --
[download]

s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
+.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e

In reply to Re^3: PerlCritic, $_ and map by Skeeve
in thread PerlCritic, $_ and map by chexmix

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.


Welcome to the Monastery
	PerlMonks