Always curious, I wondered if the apparently complex lookahead logic proposed by ikegami and happy.barney would actually save time over your original approach, ignoring, as we should not, that your original approach made some bold assumptions about where the final underscore would appear. I factored out the final uppercasing to make the code more nearly comparable, and came up with 
use Benchmark('countit');

$code = '$str =~ s/(?<=[a-z])(?=[A-Z])/_/g';
$t = countit(5, '$str="BuyACaseOfCamels";' . $code);
$count = $t->iters ;
print "$count loops of $code\n";

$code = '$str =~ s/([a-z]+)(?=(.?))/ $1 . (length($2) ? "_" : "") /ge'
+;
$t = countit(5, '$str="BuyACaseOfCamels";' . $code);
$count = $t->iters ;
print "$count loops of $code\n";

$code = '$str =~ s/([a-z]+)/$1_/g; $str =~ s/_$//';
$t = countit(5, '$str="BuyACaseOfCamels";' . $code);
$count = $t->iters ;
print "$count loops of $code\n";

[download]
I was a bit surprised at the results. 
  perl ccase.pl
1686588 loops of $str =~ s/(?<=[a-z])(?=[A-Z])/_/g
1194666 loops of $str =~ s/([a-z]+)(?=(.?))/ $1 . (length($2) ? "_" : 
+"") /ge
1520477 loops of $str =~ s/([a-z]+)/$1_/g; $str =~ s/_$//

  perl ccase.pl
1793776 loops of $str =~ s/(?<=[a-z])(?=[A-Z])/_/g
1286561 loops of $str =~ s/([a-z]+)(?=(.?))/ $1 . (length($2) ? "_" : 
+"") /ge
1466174 loops of $str =~ s/([a-z]+)/$1_/g; $str =~ s/_$//

  perl ccase.pl
1760558 loops of $str =~ s/(?<=[a-z])(?=[A-Z])/_/g
1336044 loops of $str =~ s/([a-z]+)(?=(.?))/ $1 . (length($2) ? "_" : 
+"") /ge
1492832 loops of $str =~ s/([a-z]+)/$1_/g; $str =~ s/_$//

[download]
Over three runs, the counts varied slightly, but happy.barney's code consistently outperformed your original code, and ikegami's code was only slightly less peppy than yours, a fair tradeoff for doing a better job of trimming the final underscore. I, for one, am impressed at how well the regular expression engine can perform.

In reply to Re: global match except last one by jpl
in thread global match except last one by utku

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.