Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles; site hpspkla.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tikal!hplsla!hpspkla!styborsk
From: styborsk@hpspkla.UUCP (styborsk)
Newsgroups: net.lang.c
Subject: Re: Re: C bites / programming style [if
Message-ID: <42900001@hpspkla.UUCP>
Date: Fri, 6-Sep-85 12:09:00 EDT
Article-I.D.: hpspkla.42900001
Posted: Fri Sep  6 12:09:00 1985
Date-Received: Sat, 14-Sep-85 17:37:35 EDT
References: <418@phri.UUCP>
Lines: 16
Nf-ID: #R:phri:-41800:hpspkla:42900001:000:642
Nf-From: hpspkla!styborsk    Sep  6 09:09:00 1985


This style makes a lot of sense if you look at it as follows.
The body of the if statement is ONE STATEMENT, either a single, simple 
statement such as "x = 1;" or a compound statement such as
	{
	x = 1;
	y = 2;
	}
or even a null statement such as ";".  In fact, the body of a while, for, etc.
falls into the same mold and everything becomes very consistent (which is very
nice if you are writing a package for an editor like Emacs to help you type 
your code).
When we first tried to standardize our coding style, this looked strange to me
too, but it kind of grows on you (like a fungus :-).
Randy Styborski
{ihnp4!hpfcla!}hpspkla!styborsk