Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!pdxgate!parsely!agora!intelhf!ichips!inews!nevin!bhoughto
From: bhoughto@nevin.intel.com (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: Evaluation of if's
Message-ID: <4727@inews.intel.com>
Date: 15 Jun 91 19:50:10 GMT
References: <1991Jun7.232119.17834@cs.ucla.edu> <1991Jun13.184843.508@ulkyvx.bitnet> <20575@crdgw1.crd.ge.com>
Sender: news@inews.intel.com
Distribution: usa
Organization: Intel Corp, Chandler, AZ
Lines: 25

In article <20575@crdgw1.crd.ge.com> volpe@camelback.crd.ge.com (Christopher R Volpe) writes:
>In article <1991Jun13.184843.508@ulkyvx.bitnet>, pgheit01@ulkyvx.bitnet writes:
>|>*ALWAYS* (unless you tell it not to) 
>
>How do you tell it not to short circuit "&&" or "||"??? You can't.

Not as such, but,

	... ( e1 && e2 ) ...

is the same as

	v1 = e1;
	v2 = e2;
	... ( v1 && v2 ) ...

If you want the order of evaluation of expressions
to be defined, then define the order of evaluation by
evaluating them in that order.  The language defines
many ways to evaluate expressions in a defined order.

				--Blair
				  "It won't kill you, nor
				   will anyone who has anything
				   better to do laugh at you."