Interesting. Determing a dependency on evaluation order seems like something a compiler can't possibly do in all cases. For example it might figure out

func(++i,i++)

but what about

func(f(),g())

and f and g are function pointers that aren't known at compile-time? Oh well. I guess saying the compiler should error out for the simple cases is better for the user than just having the behavior undefined. Maybe the doc should say some dependencies might not be detected (or detectable) by the compiler.

"Miguel Ferreira Simões" <Kobold@netcabo.pt> wrote in message news:cm514a$uf2$1@digitaldaemon.com...

Hi,

I've been searching the documentation and I found:

"Unless otherwise specified, the implementation is free to evaluate the components of an expression in any order. It is an error to depend on order of evaluation when it is not specified. For example, the following is illegal: func(++i, ++i)"

Isn't it supposed to evaluate function parameters from right to left? Isn't it that the c/c++ way?

Thanks.

--
Miguel Ferreira Simoes