Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!caen!umich!bushido!dbc
From: dbc@bushido.uucp (Dave Caswell)
Newsgroups: comp.lang.c
Subject: Re: Coding Standards.  was: a style question
Message-ID: <1990Nov18.034120.2963@bushido.uucp>
Date: 18 Nov 90 03:41:20 GMT
References: <1990Oct23.160116.10299@athena.mit.edu> <13@christmas.UUCP> <14369@smoke.brl.mil> <1990Nov10.191840.21113@clear.com> <7267@hub.ucsb.edu>
Organization: Bushido Systems of Ann Arbor, Michigan.
Lines: 17

.At Clear we have instituded a style standard which
.all our engineers follow.  This standard specifies how indenting
.should be done, how variables, functions and types should be named.
.I specifies that functions should have single entrance and single
.exit points, and that functions should not be much longer then
.one page.  It specifies a documentation style and demands that
.comments always be placed on closing braces.  etc. etc.

In my opinion anyone who wants to standardize simple formatting considerations
had better write a program to translate arbitrary code into that standard.

On the other hand rules like having a single entrance and exit point are good
ones.  They should be written down and strictly enforced.


-- 
David Caswell                             dbc%bushido.uucp@umich.edu