Order of evaluation - aka hidden undefined behaviours.

[Timon Gehr]

On 09/27/2012 01:43 PM, bearophile wrote:
> Walter Bright:
>
>> The best order is the one that generates the fewest temporaries, and
>> that's the order that should be defined for D.
>
> Java and Python and C# give a precedent, maybe many programmers expect a
> behavior like those ones.
>

Well, those can use a calling convention that optimally fits the
evaluation order, as they do not provide zero-overhead interaction with
C code.