Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site unc.UUCP
Path: utzoo!linus!decvax!duke!mcnc!tim@unc.UUCP (Tim Maroney)
From: tim@unc.UUCP
Newsgroups: net.unix,net.lang.c
Subject: Re: typedefs, etc.
Message-ID: <6479@unc.UUCP>
Date: Fri, 30-Dec-83 17:24:58 EST
Article-I.D.: unc.6479
Posted: Fri Dec 30 17:24:58 1983
Date-Received: Sun, 1-Jan-84 02:07:35 EST
References: <1165@cincy.UUCP>
Organization: CS Dept., U. of N. Carolina at Chapel Hill
Lines: 16

Indeed, you could make a case that the conditional form

	if ( a == b ) return( TRUE );
	else return( FALSE );

is the hacky one, and not

	return( a == b );

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
duke!unc!tim (USENET), tim.unc@csnet-relay (ARPA)