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

Steve_Kilbane@cegelecproj.co.uk (Steve_Kilbane)
Wed, 26 Jul 1995 07:20:17 GMT

          From comp.compilers

Related articles
[3 earlier articles]
Re: Order of argument evaluation in C++, etc. hbaker@netcom.com (1995-07-18)
Re: Order of argument evaluation in C++, etc. stefan.monnier@epfl.ch (Stefan Monnier) (1995-07-20)
Re: Order of argument evaluation in C++, etc. dmk@dmk.com (1995-07-21)
Re: Order of argument evaluation in C++, etc. jhallen@world.std.com (1995-07-21)
Re: Order of argument evaluation in C++, etc. hbaker@netcom.com (1995-07-26)
Re: Order of argument evaluation in C++, etc. karlcz@moraine.hip.berkeley.edu (1995-07-26)
Re: Order of argument evaluation in C++, etc. Steve_Kilbane@cegelecproj.co.uk (1995-07-26)
Re: Order of argument evaluation in C++, etc. chase@centerline.com (1995-07-28)
Re: Order of argument evaluation in C++, etc. davids@ICSI.Berkeley.EDU (1995-07-30)
Re: Order of argument evaluation in C++, etc. dave@occl-cam.demon.co.uk (Dave Lloyd) (1995-07-31)
Re: Order of argument evaluation in C++, etc. jthill@netcom.com (1995-08-03)
Re: Order of argument evaluation in C++, etc. chase@centerline.com (1995-08-07)
Re: Order of argument evaluation in C++, etc. hbaker@netcom.com (1995-08-08)
[33 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: Steve_Kilbane@cegelecproj.co.uk (Steve_Kilbane)
Keywords: C++, optimize
Organization: DSDIC Team, Cegelec Projects Ltd.
References: 95-07-068 95-07-141
Date: Wed, 26 Jul 1995 07:20:17 GMT

Henry Baker <hbaker@netcom.com> wrote:
>For the rest of the time, I think that the vast majority of C++ programmers
>would sleep much better if the order of evaluation were nailed down as some
>depth first ordering of the expression, thus allowing a simple LIFO
>allocation of the (caller's) temporaries.


Well, *I'd* be happier if the execution order was nailed down somehow.
It doesn't matter how fast the code is that your compiler generates, if
no-one understands the language intricacies well enough to write code
that'll actually work.


jhallen@world.std.com (Joseph H Allen) writes:
> More syntax could easily be added to
> force various orders of evluation:
>
> foo(parallel(x,y,leftright(z,q,parallel(a,b))))


[ cough! ] Good grief. (a) Why does the keyword "register" come to mind
at this point? (b) I can see this causing nightmares for programmers.
How are you going to debug this?


steve [ who missed earlier posts, btw... ]


--
<Steve_Kilbane@cegelecproj.co.uk>
--


Post a followup to this message

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