[Neworleans-pm] Perl optimization article

[James Keenan]

> Message: 2
> Date: Mon, 25 Oct 2004 23:12:58 -0500
> From: Simon Dorfman <EmailLists at SimonDorfman.com>
> Subject: [Neworleans-pm] Perl optimization article
> To: <neworleans-pm at mail.pm.org>
> Message-ID: <BDA338FA.12BC9%EmailLists at SimonDorfman.com>
> Content-Type: text/plain;	charset="ISO-8859-1"
>
> http://www-106.ibm.com/developerworks/library/l-optperl.html
>
>

You should note that this article has been subjected to some scorching 
criticisms on comp.lang.perl.misc starting on 10/23/04.  Here, for 
example, is what Uri Guttman wrote:

  "so many misconceptions about perl that i can't even start.  and
         he misses so many ways to optimize perl as well.

         no mention of the Benchmark.pm module.

         perl bytecode is generally useless and doesn't give much speedup

         choosing a better algorithm and/or data structure is the best
         way to optimize code in any language. if you think perl 's speed
         is the problem then you either chose the wrong language or don't
         know how to code perl efficiently. examining bytecode is silly
         in this context. it still won't show you which ops are the
         bottlenecks.

         the speed difference between single and double quoted strings is
         negligible. try a benchmark yourself. double quoted strings are
         converted to a join of the string parts at compile time so there
         is no runtime loss for simple strings."

Jim Keenan