D and expression evaluation order.

[Bruno Medeiros]

Sean Kelly wrote:
> 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.  Can a 
> strong parallel be drawn between D and any of the languages you mention, 
> insofar as this issue is concerned?
> 
> 
> Sean

C# does support operator overload. Dunno about Python and Ruby.
But I don't see how operator overloading or calling conventions would 
have any effect on having a completely defined expression order of 
evaluation. Indeed, I don't think it makes any difference.

-- 
Bruno Medeiros - MSc in CS/E student
http://www.prowiki.org/wiki4d/wiki.cgi?BrunoMedeiros#D