Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP
Path: utzoo!linus!decvax!genrad!mit-eddie!barmar
From: barmar@mit-eddie.UUCP (Barry Margolin)
Newsgroups: net.unix,net.lang.c
Subject: Re: typedefs, functions returning pointers to functions
Message-ID: <1097@mit-eddie.UUCP>
Date: Thu, 29-Dec-83 01:47:09 EST
Article-I.D.: mit-eddi.1097
Posted: Thu Dec 29 01:47:09 1983
Date-Received: Fri, 30-Dec-83 00:43:12 EST
References: <2035@fortune.UUCP> <2466@azure.UUCP>
Organization: MIT, Cambridge, MA
Lines: 21

While I agree with Steve Summit's message in general, I have to take
exception with him on one of his points and side with the programming
teacher.  I find nothing cryptic in

	return (a == b)

It merely means "return whether a and b are equal".  Were I a
programming teacher I wouldn't go so far as to take points of for saying

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

I suppose that some theory of good programming style might dictate that
conditionals should only be used in places where only conditionals are
expected, such as in the test in an "if" or "for" statement.  I don't
happen to agree with this, but I will defend to the death someone's
right to program this way.
-- 
			Barry Margolin
			ARPA: barmar@MIT-Multics
			UUCP: ..!genrad!mit-eddie!barmar