in reply to Optimizing existing Perl code (in practise)
If it has been said once it has been said a thousand times
"beware of premature optimization!" Ask
yourself, "does this really need to be faster? Really?"
I think a very important item to optimize is code maintainabibilty - how easy is it to extend your program and fix bugs that break your code?
So, how do i optimize my Perl code? I generally don't (but i do try to get it right the first time - measure twice, cut once). If i do, it is to replace areas of wheel re-invention with CPAN modules, or to refactor items into classes to improve robustness. If i wanted faster code i would port it to C instead, but since most of what i write relies on database and web servers, Perl is 90% of the time not the bottleneck.
jeffa
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: (jeffa) Re: Optimizing existing Perl code (in practise)
by cybear (Monk) on Aug 19, 2002 at 10:56 UTC | |
by Aristotle (Chancellor) on Aug 19, 2002 at 11:07 UTC | |
by cybear (Monk) on Aug 19, 2002 at 14:01 UTC |
In Section
Seekers of Perl Wisdom