Binaryworld - C++ Compiler Trap, Indeterminism in function argument evaluation ... [ C/C++/ASM -> Misc ]

int i=0;
printf("%d %d %d %d", i++, i==1, i, ++i);

Its giving this output:
On Sun Solaris 8:
0 1 2 2
On Linux:
1 1 1 1
On Windows:
0 1 1 2

Some thoughts:

Incr/decr ops have side effect so arg list values are undefined in this case. It's an excellent example of a classic trap with evaluation order. You may have different results not only on Unix/Windows but also on different implementation on the same system.
Be careful with side effect operations.

C language/compiler tells that there is no finite rule for this type of evaluation

Multiple side effects on the SAME variable between sequence points are ALWAYS UNDEFINED within the C language.

http://c-faq.com/expr/evalorder1.html