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

Robert Bradshaw robertwb at math.washington.edu
Thu Mar 17 22:26:43 CET 2011

On Thu, Mar 17, 2011 at 2:25 PM, Stefan Behnel <stefan_ml at behnel.de> wrote:
> Robert Bradshaw, 17.03.2011 05:05:
>> On Wed, Mar 16, 2011 at 7:53 AM, Stefan Behnel wrote:
>>> I'm actually leaning towards not guaranteeing the order of execution if C
>>> doesn't do it either. If this is really required, it's easy to work
>>> around
>>> for users, but it's severely hard to fix for Cython in all cases, and the
>>> gain is truly small. After all, we'd only make it easier for users to
>>> write
>>> bad code.
>> Yep. Lets keep the code in for the above case.
> Erm, the current status is that we try to guarantee the order by pushing
> everything into temps, thus breaking Sage. What code exactly did you intend
> to keep here?

I was thinking about guarding it with an if False (or flag in Options.py).

- Robert

More information about the cython-devel mailing list