Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site reed.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!reed!alexis
From: alexis@reed.UUCP (Alexis Dimitriadis)
Newsgroups: net.lang.c
Subject: Re: C style
Message-ID: <2081@reed.UUCP>
Date: Wed, 30-Oct-85 23:27:05 EST
Article-I.D.: reed.2081
Posted: Wed Oct 30 23:27:05 1985
Date-Received: Sat, 2-Nov-85 04:27:30 EST
References: <1556@brl-tgr> <2600023@ccvaxa> <259@3comvax.UUCP> <538@ttrdc.UUCP>
Reply-To: alexis@reed.UUCP (Alexis Dimitriadis)
Organization: Reed College, Portland, Oregon
Lines: 25

In article <538@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes:
>[...] The && operator
>doesn't GUARANTEE the chronological order of evaluation is going to be left
>to right, if you have a screwball compiler (though it most probably will be).

Dear Dan:
  You have just inserted your foot in your mouth, in full view of the users
at over 2000 sites around the world.  Observe:

	"Expressions connected by && or || are evaluated left to right, and
	evaluation stops as soon as the truth or falsehood of the result is
	known.  These properties are critical to writing programs that work."
	[K&R, p.38]

  Why, oh why, do we have to endlessly argue fundamental language features?
Please check your facts before you enlighten the net with your wisdom, folks!

Alexis Dimitriadis
-- 
_______________________________________________
  As soon as I get a full time job, the opinions expressed above
will attach themselves to my employer, who will never be rid of
them again.
				alexis @ reed
    {decvax,ihnp4,ucbcad,uw-beaver}!tektronix!reed.UUCP