Here's another way that avoids a lot of fuss. It's rather like quent's but avoids
unneeded churning on the counter.
It also works with multicharacter substitutions and, with some odd results unless
the start count < 1, the target can be a regex.
#!/usr/bin/perl -w # -*-Perl-*-
use strict;
sub zaxo {
my ($str,$chr,$new,$nbr)=@_;
$str=~s/$chr/(--$nbr>0)?$chr:$new/geo;
$str;
}
my $s = "Terence and Philip are sweet\n";
my $c = 'e';
my $r = 1;
my $n = 3;
print zaxo( $s,$c,$r,$n);
exit;
Against the bbfu benchmark posted above (corrected &mine output) I get:
Benchmark: timing 500000 iterations of BBFU'S, MINE, Quent's, Zaxo's..
+.<BR/>
BBFU'S: 12 wallclock secs (12.18 usr + 0.05 sys = 12.23 CPU)
MINE: 13 wallclock secs (12.32 usr + 0.06 sys = 12.38 CPU)
Quent's: 13 wallclock secs (13.40 usr + 0.03 sys = 13.43 CPU)
Zaxo's: 10 wallclock secs (10.59 usr + 0.00 sys = 10.59 CPU)
I must to agree with MeowChow that this is a litmussy kind of question.
After Compline,
Zaxo
-
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.