Looks like I'm wrong about being able to bless a s{}{} statement. That would be truly convenient. I'll change that in the tutorial.
In your benchmarking, lots of the time *is* taken up by the function call. Here's what I ran to prove that. (This has to be done in the Cleaner package, for obvious reasons.):
timethese(1000000, {
'blessed' => sub { my $bar = $foo; $c->clean($foo); },
'normal' => sub { my $bar = $foo; $bar =~ s/^\s+|\s$//g; },
'super' => sub { my $bar = $foo; $bar =~ s/$c//g; },
});
There's not nearly the performance penalty involved:
Benchmark: timing 1000000 iterations of blessed, normal, super...
blessed: 10 wallclock secs ( 9.83 usr + 0.00 sys = 9.83 CPU)
normal: 4 wallclock secs ( 5.42 usr + 0.00 sys = 5.42 CPU)
super: 7 wallclock secs ( 6.71 usr + 0.00 sys = 6.71 CPU)
I suspect that if the regex were more complicated (and $foo were much longer), the difference wouldn't be quite as intense.
-
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.