[Cython] Out of order side effects of argument evaluation in function calls (ticket #654)

Greg Ewing greg.ewing at canterbury.ac.nz
Thu Mar 17 00:13:19 CET 2011

Stefan Behnel wrote:
> That means that the average 
> innocent future maintainer could break the code by manually rearranging 
> the expression in a way that's perfectly valid mathematically,

Another thing is that when the subexpressions concerned
are function arguments, it only works if the order of the
arguments happens to be the same as the required order of
evaluation. Changes in the function signature can therefore
lead to subtle breakage.


More information about the cython-devel mailing list