My approach is that by not forcing myself to stick with the same style as the original developer, I can see (albeit not with a perfect success rate) who put what where. If the SQL query has uppercase keywords then I probably wrote it (or rewrote it).
More importantly, if something has stopped working and the query is all lowercase, one of the other guys could probably explain what has changed and why, rather than me trying to determine whether I am at fault. CVS doesn't get used much here (except in the stuff that is basically my exclusive area), so those factors will play less of a part for someone that has change logs etc.
- Spelling is a demanding task that requies you full attention.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||