Well, why not? 
use Benchmark;
 
undef $/;
open DATA, "/home/jeroen/texs/review/reviewnew.tex" or die $!; #just s
+ome lengthy manuscript
$str = <DATA>;
open DUMP, ">/dev/null";
 
timethese( -1, {'regex' =>
  sub {
   $a = $str;
   print DUMP map "$_\n", $a=~/\G(.{1,80})/gs;
  },
           'substr' =>
  sub {
    $a = $str; $b='';
    $b .= substr( $a, 0, 80, '')."\n" while length($a) >80;
    print DUMP "$b$a";
  }
});

#givesBenchmark: running regex, substr, each for at least 1 CPU second
+s...
     regex:  1 wallclock secs ( 1.05 usr +  0.01 sys =  1.06 CPU) @ 28
+7.74/s (n=305)
    substr:  1 wallclock secs ( 1.26 usr +  0.01 sys =  1.27 CPU) @ 55
+6.69/s (n=707)

#This changes a bit when leaving the map out:

Benchmark: running regex, substr, each for at least 1 CPU seconds...
     regex:  2 wallclock secs ( 1.06 usr +  0.00 sys =  1.06 CPU) @ 39
+6.23/s (n=420)
    substr:  2 wallclock secs ( 1.04 usr +  0.02 sys =  1.06 CPU) @ 54
+7.17/s (n=580)

#I left the print out@substr at first (didn't want to test
# print), but putting it back in gives:

Benchmark: running regex, substr, each for at least 1 CPU seconds...
     regex:  1 wallclock secs ( 1.30 usr +  0.01 sys =  1.31 CPU) @ 36
+6.41/s (n=480)
    substr:  1 wallclock secs ( 1.06 usr +  0.02 sys =  1.08 CPU) @ 47
+3.15/s (n=511)

#I added a better comparison:
        Rate regmap  regex fixreg substr
regmap 285/s     --   -19%   -22%   -56%
regex  350/s    23%     --    -4%   -46%
fixreg 364/s    28%     4%     --   -44%
substr 650/s   128%    86%    78%     --

[download]
Apparently, the substr is just too efficient compared to regex. End the print is only a bit inefficient compared to storing stuff in memory.

Jeroen
"We are not alone"(FZ)

In reply to Re:{4} how do I line-wrap while copying to stdout? by jeroenes
in thread how do I line-wrap while copying to stdout? by ams

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.