Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!vax135!cornell!uw-beaver!tektronix!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!cottrell@nbs-vms.ARPA
From: cottrell@nbs-vms.ARPA
Newsgroups: net.lang.c
Subject: Style Flambe
Message-ID: <7907@brl-tgr.ARPA>
Date: Thu, 31-Jan-85 17:43:44 EST
Article-I.D.: brl-tgr.7907
Posted: Thu Jan 31 17:43:44 1985
Date-Received: Thu, 7-Feb-85 03:39:17 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 20

/*
Mark Terribile replies to my plea for form feeds: 

> 	And please DON'T put the maddog form feeds in.  White space
> ought to communicate something just as much as code.  With the proper
> use of white space and the proper and consistant placement of blocks
> of code and the conditions that govern them, program structure is
> communicated ... but FORMFEEDS introduce spacing of random lengths
> in synchronization NOT with the structure of the program but rather
> in synchronization with an ARBITRARY and IRRELEVANT event -- the
> passing of a fold in the paper on which the listing (if any) may be printed.

Some people rarely make listings but I do. I regard a paper fold as VERY
significant if I have to keep flipping the maddog page to see the other
half of a IF or WHILE. Opinion being what it is, this doesn't bother
everyone, including my own brother. However, the minute I get my hands
on a program, that's what I do. Funxions should be small enuf to fit
on a page, just as lines should be small enuf to fit on a tty. I often
put many funxions on a page if they fit in order to save paper.
*/