Re: [BUG] Bad #define, nonportable C, missing {}

[Andreas Schwab <schwab@suse.de>]

Jan Hudec <bulb@ucw.cz> writes:

|> > On Wed, Nov 21, 2001 at 12:40:17PM +0000, vda wrote:
|> > If you wanna do this type of cleanup, you can take it one step forward;
|> > remember that the order of evaluation of foo and bar doesn't have to be
|> > {foo => bar} so it can be {bar => foo}  I hope gcc's behaviour doesn't
|> > change under our feet.
|> > 
|> > 	a = foo (i) + bar (j);
|> > 
|> > .. sprinkle some pointer arithmetic over there for fun ;)
|> 
|> AFAIK here the order *IS* defined. + operator is evaluated left to right

No.  It is undefined which of the operator's arguments is evaluated first,
unless it is defined otherwise (only for ||, && and comma).

Andreas.

-- 
Andreas Schwab                                  "And now for something
Andreas.Schwab@suse.de				completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5