Messages in this thread | | | Subject | Re: [BUG] Bad #define, nonportable C, missing {} | From | Andreas Schwab <> | Date | 21 Nov 2001 15:19:13 +0100 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |