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!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!cottrell@NBS-VMS
From: cottrell@NBS-VMS
Newsgroups: net.lang.c
Subject: The wonders of C
Message-ID: <9509@brl-tgr.ARPA>
Date: Tue, 26-Mar-85 14:08:30 EST
Article-I.D.: brl-tgr.9509
Posted: Tue Mar 26 14:08:30 1985
Date-Received: Thu, 28-Mar-85 02:02:55 EST
Sender: news@brl-tgr.ARPA
Lines: 20

/*
> It seems to me that the normally-cited "save keystrokes" reason for
> the =/== choice cannot be correct.  If it were, wouldn't the choice for
> the &/&& and |/|| operators be reversed?  &&'s are much more common than
> &'s in almost all C code I have seen.

It depends on how you write code. I do lotsa bit twiddling, therefore I
got lotsa `&' & `|'. I avoid multiple condition tests, therefore I 
seldom have `&&' & `||'. 

> It also seems clear that saving keystrokes is almost never a valid concern.
> What needs to be optimized is readability.  Even in the case of my own
> code, let alone others, I read it much more often than I write it.

There are thos of us who consider verbosity the scourge of readability.
`Begin' & `end', e.g.,just clutter up the listing & spread it out more. I
HAVE been bitten by saying `if (c = NL)' a lot tho. Oh well.

	jim		cottrell@nbs
*/