Out of order side effects of non-trivial arguments in function calls

[robertwb]

cdef int f():
    print "f"

def g():
    print "g"

cdef foo(int x, object o):
    pass

foo(f(), g())

There may be others sitting out there due to inline expressions vs. temporary variables.

[scoder]

Fixed here:

 https://github.com/cython/cython/commit/a94909c1876cfece04162cd617e6e57eb1299e84

Test case:

 https://github.com/cython/cython/commit/297f652d5ab3f166f98df3d1571ff1c883f7cc55

[robertwb]

This still has some issues.

[robertwb]

I was wondering how C enforced this without performance loss, and came across  http://stackoverflow.com/questions/2934904/order-of-evaluation-in-c-function-parameters

[scoder]

Interesting. So, would you suggest we follow the same scheme in Cython? I wouldn't object.

[scoder]

It was decided that C functions should obey C calling semantics. The order of the evaluation of their arguments is therefore undefined.