Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!hub.ucsb.edu!ucsbuxa!6600dt
From: 6600dt@ucsbuxa.ucsb.edu (David Goggin)
Newsgroups: comp.lang.c
Subject: Re: Coding Standards.  was: a style question
Message-ID: <7267@hub.ucsb.edu>
Date: 16 Nov 90 21:31:15 GMT
References: <1990Oct23.160116.10299@athena.mit.edu> <13@christmas.UUCP> <14369@smoke.brl.mil> <1990Nov10.191840.21113@clear.com>
Sender: news@hub.ucsb.edu
Lines: 21

In article <1990Nov10.191840.21113@clear.com> rmartin@clear.com (Bob Martin) writes:

>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.

I don't think I'd
like to have a format forced on me like that.  I
think, however, I _well-designed_ standard does go a
long way in clearing up the problem.  I would
reccommend a standard that is thought out carefully
in advance, to be most logical in showing the
structure of code, as well as aestheticaly pleasing
(a big factor for me.)

*dt*
6600dt@ucsbuxa.bitnet