Optimizing Perl

An anonymous reader writes "Perl is an incredibly flexible language, but its ease of use can lead to some sloppy and lazy programming habits. We're all guilty of them, but there are some quick steps you can take to improve the performance of your Perl applications. This article looks at the key areas of optimization, which solutions work and which don't, and how to continue to build and extend your applications with optimization and speed in mind."

Comments

Error 400

[hattmoward]

Proxy Error: Unable to connect to remote host "ltsgnd001k.sby.ibm.com" or host not responding - URL "http://ltsgnd001k.sby.ibm.com/developerworks/libr ary/l-optperl.html?ca=dgr-lnxw01OptPerl", errno: 79

Does this mean you can't optimize Perl? =D

Disclaimer: I use Perl almost exclusively for programming.

Best PERL Optimization trick ever:

[torpor]

rm -rf /usr/bin/perl

{ Just Use Python! :) }

Re:Best PERL Optimization trick ever:

[the quick brown fox]

It's a little ironic that you wrapped "Just Use Python! :)" in curly braces, isn't it?

Universal Guilt

[Anonymous Coward]

Perl is an incredibly flexible language, but its ease of use can lead to some sloppy and lazy programming habits. We're all guilty of them

Are you accusing me of writing PERL? Come over here and say that again!

Perl is the only language ...

[Anonymous Coward]

... where the optimized code is easier to read.

Re:No offense

[Anonymous Coward]

I never said I or any programmer writes perfect code, however I feel the blame for lazy and/or sloppy mistakes should be upon the programmer, not the tool.

My approach to sex is the same to programming: have fun, be kinky, but don't be lazy and take proper precautions. I don't blame the girl if I'm a bad lay.

Why the hostility about being a geek and not getting laid? You realize you're arguing with an anonymous programmer on slashdot about programming... not exactly a non-geeky thing to do.

My favorite perl joke:

[mshiltonj]

DAY 1:
Manager: How many lines of code did you write today?
Developer: One.

DAY 2:
Manager: How many lines of code did you write today?
Developer: One.

Day 3:
Manager: How many lines of code did you write today?
Developer: One.
Manager: Are you telling me that in three days you've only mangaged to write three lines of code?
Developer: You don't understand -- I've been working on the same line of code all three days.
Manager: (pauses) You're writing in perl again, aren't you?