> http://www.piclist.com/techref/language/ccpp/10CStyle.htm

Nicely worded, but IMHO otherwise just a list of crap.

First: such rules are never absolute, everything is relative to the
intended audience. For instance: in a freshmen C course a comment like
   i++;  // Add one to i  
might actually be a good idea. A comment should explain something beyond
the code, but what the code explains is audience-dependent. Hence
meaningfull comments are too. And note that // is not a comment in C,
only in C99, which is not exactly the current mainstream of C.

Then: "Thou shalt properly indent programs, each subservient function
being indented one level more than its master." What is a subservient
fucntion? If it is lower in the (inverted) call tree, how do I indent
mutually recursive functions? Or are they forbidden?

I'll leave bashing the other ones as an excercise to the readers :)

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 


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