I didn't turn it into a function call arbitrarily. In
fact, I explained my reasoning for doing so. I was attempting to
compare the speed of File::Slurp to the idiomatic slurp. I was not
attempting to measure the speed of Perl's subroutine calls, much less
loading of modules. It's already well-established that these things
A fairer benchmark would compare the slurp methods as they'll be
used. Since idiomatic slurp doesn't require a function call, it seems
sensible not to add the extra overhead into the benchmark.
Unfortunately the modular solution can't escape Perl's function calls,
so the overhead must be factored into its performance.
I'm sure there's a point where File::Slurp's efficiency overwhelms
the function call penalty. It would be interesting to see where that
point actually is, even though it probably varies from one system to
The original poster's argument is that their system slurps files
that fall below the break-even point for File::Slurp. It's therefore
more efficient (in runtime speed) to use inline idiomatic slurp.
-- Rocco Caputo - http://poe.perl.org/