Some quick benchmarking shows your solution to be about half as
fast compared to mine.
#!/usr/bin/perl
use strict;
use warnings;
use Benchmark qw /cmpthese/;
our @files = qw {
/etc/passwd
one/two/three/four/five/six.a
file
a/very/deep/file/indeed/deeper/than/you/may/think/really
};
cmpthese -5 => {
abigail => 'foreach my $f (@files) {
my $fn = (split m{/} => $f) [-1]
}',
markm => 'foreach my $f (@files) {
my ($fn) = $f =~ /([^\/]+)\z/
}',
};
__END__
Benchmark: running abigail, markm for at least 5 CPU seconds...
abigail: 5 wallclock secs ( 5.19 usr + 0.00 sys = 5.19 CPU) @ 68
+404.24/s (n=355018)
markm: 6 wallclock secs ( 5.23 usr + 0.00 sys = 5.23 CPU) @ 34
+427.53/s (n=180056)
Rate markm abigail
markm 34428/s -- -50%
abigail 68404/s 99% --
Abigail
-
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.
|