Perl: the Markov chain saw | |
PerlMonks |
Re: Re: Code for readablity or fewer lines?by unixwzrd (Beadle) |
on Feb 27, 2001 at 22:09 UTC ( [id://61117]=note: print w/replies, xml ) | Need Help?? |
I'll second that footpad, coding for clarity is best. People
time is more expensive than machine time, and the divergence
between the two gets wider every day.
Optimization is good to the point where code starts to lose clarity. Unless the application has to be really optimized. It optimization is the case, then add copius comments so when you or someone else comes back a year later to enhance or fix it - again people time. I also agree, that I like to over-comment. A year from now I want to know what I was thinking when I go back and look at my code. Besides, comments don't add anything to the actual executable, they are discarded at compile time. Mike - mps@discomsys.com
"The two most common elements in the universe are hydrogen... and stupidity."
In Section
Seekers of Perl Wisdom
|
|