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

Greg Ewing greg.ewing at canterbury.ac.nz
Sat Mar 12 00:37:11 CET 2011


Stefan Behnel wrote:

> To be a little clearer here, it's a problem in C for example with struct 
> values. Copying them by value into a temp variable can be expensive, 
> potentially twice as expensive as simply passing them into the function 
> normally.

What are you actually proposing to do here? Anything that
Cython does in the generated code to guarantee evaluation
order is going to involve using temp variables, and thus
incur the same overhead.

-- 
Greg


More information about the cython-devel mailing list