Actually, I think I prefer your layout too--and I can't exactly put my finger on why either:)

Ew. That that sprinkles eval blocks all over. That's also suboptimal. The original poster had the best version already. I fixed my own code to be nearly similar except that it doesn't benefit from perl's ability to compile a static regex only once. Your code is a static regex but you're imposing eval {} at each match point.

An entirely different route might be to do some code generation so that the common parts are written only once, eval blocks aren't sprinked all over the place and the world is good again. The only issue is that now its not pretty anymore.

# Keep $escape somewhere or give it a proper name.
my $escape = eval "sub {\n".join("\n",map "    \$_[0] =~ s/\\$_/\\\\$_
+/g;", qw/t r n f/)."\n};";

$escape->( $text );
[download]

you're imposing eval {} at each match point

Sorry, no. You're confusing /e with /ee. There's no evaling with /e.

Makeshifts last the longest.

Huh. I wouldn't have guessed. The first /e isn't an eval, any other /e's are eval string blocks with all of the $@ overwriting semantics.