Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ucbcad.UUCP
Path: utzoo!linus!decvax!microsoft!uw-beaver!tektronix!ucbcad!ucbesvax.turner
From: ucbesvax.turner@ucbcad.UUCP
Newsgroups: net.unix
Subject: Re: typedefs, etc. - (nf)
Message-ID: <1213@ucbcad.UUCP>
Date: Mon, 9-Jan-84 00:53:44 EST
Article-I.D.: ucbcad.1213
Posted: Mon Jan  9 00:53:44 1984
Date-Received: Thu, 5-Jan-84 01:15:41 EST
Sender: notes@ucbcad.UUCP
Organization: UC Berkeley CAD Group
Lines: 21

#R:cincy:-116500:ucbesvax:23100005:000:853
ucbesvax!turner    Jan  2 19:20:00 1984

>   /***** ucbesvax:net.unix / unc!UUCP /  8:30 am  Dec 31, 1983*/
>   The idea of a Boolean expression is a part of all procedural languages
>   I'm familiar with, including C, Pascal, and so on.  If the programmer
>   can't understand the idea of a Boolean expression yielding a Boolean
>   value, that's his blind spot, and it will lead to inferior code.
>   --
>   Tim Maroney, University of North Carolina at Chapel Hill

I wouldn't mind if "a==b" was a Boolean expression--I would be quite happy
with "return (a==b)" if it was really Boolean.  But in C, it's not.  It's
an integer-valued expression.  See K&R, if you don't believe me--there is
no intrinsic Boolean type.

If the compiler can't understand the idea of a Boolean expression, that's
its blind spot.  It does lead to inferior code, at that.
---
Michael Turner (ucbvax!ucbesvax.turner)