D and expression evaluation order.

[Sean Kelly]

Jan Claeys wrote:
> Op Fri, 27 Apr 2007 18:42:12 -0700
> schreef Sean Kelly <sean at f4.ca>:
> 
>> Bruno Medeiros wrote:
>>> Sean Kelly wrote:
>>>> It's an issue because it's confusing, as previous discussions can 
>>>> attest.  I'm still not convinced that there is sufficient reason
>>>> to define an evaluation order, since most other languages don't
>>>> and it doesn't seem to be a problem, but I'll admit that it would
>>>> make for less confusion.
>>> What do you mean by "most other languages"? Have you seen my other
>>> post which mentions that not only Java, but C#, Python, and even
>>> Ruby all have well defined evaluation orders?
>> True.  I suppose I should have said "most other languages I've
>> used" :-p I'm wondering if it's fair to include languages that don't
>> support operator overloading though, or multiple calling
>> conventions. 
> 
> Python supports operator overloading and "multiple calling
> conventions"?  ;-)

Ah well :-)  I suppose I'm just worried we'd be trading away a potential 
for optimization for support of a coding strategy that no one should be 
using anyway.


Sean