Looks like it's slightly faster than the regexp: 
Benchmark: timing 1000000 iterations of regexp, split, substr...
    regexp: 16 wallclock secs (16.27 usr +  0.03 sys = 16.30 CPU)
     split: 17 wallclock secs (15.88 usr +  0.00 sys = 15.88 CPU)
    substr:  6 wallclock secs ( 5.32 usr +  0.00 sys =  5.32 CPU)

[download]
Hmm, substr is the winner in a big big way. Makes sense. What if we anchor the regexp?         'regexp' => sub { my($file) = $img =~ m#.*/(.*)$# } gives us 
 regexp: 17 wallclock secs (16.15 usr +  0.00 sys = 16.15 CPU)
     split: 15 wallclock secs (15.93 usr +  0.00 sys = 15.93 CPU)
    substr:  5 wallclock secs ( 5.37 usr +  0.00 sys =  5.37 CPU)

[download]
Nothing else I tried improved things.

In reply to RE: Re: Rexgrep by chromatic
in thread Rexgrep by toadi

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.