Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!felix!arcturus!evil
From: evil@arcturus.UUCP (Wade Guthrie)
Newsgroups: comp.lang.c
Subject: Re: `if (a = b)' (was Standard indentation?)
Summary: AAAAAAAHHHHHHHHH!. . .<fthwap> ~whimper~
Message-ID: <3049@arcturus>
Date: 16 Dec 88 21:23:55 GMT
References: <5@rsoft.UUCP> <1071@goofy.megatest.UUCP> <861@quintus.UUCP> <8536@alice.UUCP>
Organization: Rockwell International, Anaheim, CA
Lines: 31

The sound of a programmer trying to read a C program flinging himself
against a wall.

In article <8536@alice.UUCP>, ark@alice.UUCP (Andrew Koenig) writes:
> 	do	ch = getchar();
> 	while (ch != EOF)
> 		process(ch);
> or, with braces:
> 	do {
> 		ch = getchar();
> 	} while (ch != EOF) {
> 		process(ch);
> 	}

I really do not mean to flame this person, but the above constructions
are EXCEEDINGLY hard to read.  I much perfer the method which already
exists:

	while ( (c=getchar()) != EOF)
		process(c);

because it is easier for humans to parse (not to mention the fact that it
requires less space.


Wade Guthrie
Rockwell International
Anaheim, CA

(Rockwell doesn't necessarily believe / stand by what I'm saying; how could
they when *I* don't even know what I'm talking about???)