M Graff wrote:

> The importance of following strictly the style your employeer lays out is
> that you probably won't be the only one working on your code, and people
> have been reprimanded and/or let go because of their adamant refusal to
> follow the style guide's major points.

I agree completely. My message was written with the view of someone who
follows various clients' styles, besides writing code under my own control
using my style. 

Maybe there's another general rule (or is this a consequence of the
consistency rule): Never charge a style mid-stream. When changing or adding
to code, use the style that's already there, even if it isn't your
preference.

I still think that not only "learning" a style, be that BSD or GNU or
Microsoft, is the important thing, but rather understanding the rationale
behind every single rule. This is the part I meant with "developing your
own style". It is much easier following someone else's style if you
understand the reason and know about pros, cons and alternatives.

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist