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."
Harlan Ellison
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.