Code reviews (and standards) can also prevent cleverness (i.e.: actual code golfing in producton code). However, if the reviewer is not more experienced in the language, low performing or unnecessary constructs can still slip. I also think that there must a an automatic tool (like Perl::Critic) in the process. Btw, if you are implementing coding standards into the process, then it must be applied backwards on old code too IMHO. Lets say; if you forbid tabs, remove tab indentation from older code if it is still maintained. And column width is usually missed. I hate to see 500 chars on a code line (nope, word wrapping in an editor does not solve this shit).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||