D and expression evaluation order.

[Bruno Medeiros]

Sean Kelly wrote:
> Russell Lewis wrote:
>> Manfred Nowak wrote:
>>> Russell Lewis wrote
>>>
>>>> Why prevent optimizers from doing all that they can conceive of?
>>>
>>> This is not an issue, because the requirement is to define an order 
>>> for those cases only, where currently evaluation order matters. In 
>>> all other cases the compiler is free to choose the optimum the same 
>>> way it currently does.
>>
>> I don't understand what you're saying here; perhaps your definition 
>> was too indirect?  What are you wanting to define orders for, and what 
>> not?
>>
>> Moreover, if it's not an issue, then why did Walter bring it up? 
>> Apparently it *is* an issue.
> 
> 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.
> 
> 
> Sean

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?


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