Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mmintl.UUCP
Path: utzoo!linus!philabs!pwa-b!mmintl!franka
From: franka@mmintl.UUCP (Frank Adams)
Newsgroups: net.lang.c
Subject: Re:  C Programming Style -- New thought (\"writing code\")
Message-ID: <547@mmintl.UUCP>
Date: Mon, 29-Jul-85 16:11:12 EDT
Article-I.D.: mmintl.547
Posted: Mon Jul 29 16:11:12 1985
Date-Received: Wed, 31-Jul-85 22:38:20 EDT
References: <189@brl-tgr.ARPA> <1017@umcp-cs.UUCP>
Reply-To: franka@mmintl.UUCP (Frank Adams)
Organization: Multimate International, E. Hartford, CT
Lines: 14
Summary: Thinking about it twice helps



I no longer write code on paper first; this changed at the time I first
got access to a full screen editor.

The main advantage of writing it down first is that is gives one a second
chance to look over the code and notice mistakes.  This reason is less
significant for me than it used to be because (1) I make fewer mistakes
than I used to, and (2) I gain the same benefit (plus others) by writing
a design specification.

Usually, I use a printed listing, except for very short code (fits on a
screen) (previously, I had a 43 line screen; now I'm back down to 25.
Everything else is better now, but I miss the big screen.  Sigh.)  Using
a listing doesn't keep me from using grep; I do both.