Re: Order of argument evaluation in C++, etc.

  Henry Baker <hbaker@netcom.com> wrote:
] My personal feeling is that I agree (in this instance) with David Chase
] 100%, and would go so far as to say that far from allowing _speedups_, the
] current ambiguity in the language standards actually _guarantees_ slowdowns in
] programs which aspire to any amount of portability. The problem is that if you
] were truly paranoid, you would have to start locking and unlocking serially
] accessed data structures on the different arguments to a multi-argument
] procedure.


What's wrong with using


tmp1=argexp1;
tmp2=argexp2;
...
fun(tmp1, tmp2, ...)


instead of


fun(argexp1, argexp2, ..)


The code is less readbale, but definitely not slower.


Stefan
[I thought compilers were supposed to make programming easier, not harder.
-John]
--

Return to the comp.compilers page.
Search the comp.compilers archives again.