begin quoting Gregory K. Ruiz-Ade as of Sat, Mar 15, 2008 at 10:27:18AM -0700: > On Mar 15, 2008, at 10:00 AM, SJS wrote: > > >Some rules are helpful; but more isn't always better. You can't > >force a programmer to generate good code by choosing the right coding > >standard. > > Coding standards, however, help maintain consistency within a project > (or organization).
Yes. [snip] > Provide a couple example code snippets, and for me, that would likely > be enough. Note, also, that I am not above changing my desired style > given a compelling enough argument. :) I used to experiment a lot more with coding style differences, just to see how they'd work. I found that some styles work better (for me) in some languages than others. The downside of being super-flexible is that you never quite internalize a style to the point of being able to forget about it. Some people have a brain the size of a planet, and can spare the extra processing power to remember what the current style is supposed to be, but that wouldn't be me. I don't even think about coding style guidelines until I run across code that is inconsistent, outlandish, or just plain odd. -- Odd, as in mixed spaces and tabs, tabstops at 10, and an aversion to vowels. Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
