Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!reed!percival!nerd
From: nerd@percival.UUCP
Newsgroups: news.admin
Subject: Re: How (not) to Program in C (was Re: PD C as solution to binary groups)
Message-ID: <874@percival.UUCP>
Date: Tue, 1-Sep-87 05:05:57 EDT
Article-I.D.: percival.874
Posted: Tue Sep  1 05:05:57 1987
Date-Received: Thu, 3-Sep-87 05:52:21 EDT
References: <6960@g.ms.uky.edu> <3725@ncoast.UUCP>
Reply-To: nerd@percival.UUCP (root user)
Organization: Percy's UNIX, Portland, OR.
Lines: 17

In article <3411@zen.berkeley.edu> iverson@cory.Berkeley.EDU.UUCP (Tim Iverson) writes:
>As for Standard C Programming, I'm all for it - as long as my code is used
>as the standard.  The problem is that every other C programmer feels the
>same way about his code.

I agree, my code has to be the standard.

One thing I ocasionaly have trouble with is the formating used
by other programmers.  I have gotten used certain conventions
(placement of '{' and '}', indentation, and other details) and
thus seek out the structure of a program by standing far enough
from the printout that I see a grey shape rather than words,
then I zoom in when I need to see the details.  How about an
easily customizable version of cb(1)?  I don't realy care how
you write your code, so long as when I have to maintain it I
can view it in a format intuitive and pleasant to me.
-michael