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; },
});
[download]

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)
[download]

I suspect that if the regex were more complicated (and $foo were much longer), the difference wouldn't be quite as intense.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		&
	<		&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.