When I was younger than I am now, I had the same condescending attitude that you do towards people who comment lightly or not at all.
But then I learned from painful experience (and advice from wiser programmers) that comments have about as many bugs as code when first written, but only the bugs in code get caught, and going forward only the code is maintained. Therefore in maintainance programming, don't trust comments.
But if the maintainance programmer ignores your comments, then attempting to make bad code OK by adding comments is worse than useless. You may get warm fuzzies from having the comments, but the energy would have been better spent making the code better...
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.