Related articles |
---|
By value-result vs by reference guerin@iro.umontreal.ca (1994-04-21) |
Re: By value-result vs by reference graham@pact.srf.ac.uk (1994-04-21) |
By value-result vs by reference ssimmons@convex.com (1994-04-21) |
Re: By value-result vs by reference hbaker@netcom.com (1994-04-21) |
Re: By value-result vs by reference Dik.Winter@cwi.nl (1994-04-21) |
Re: By value-result vs by reference nebbe@lglsun.epfl.ch (1994-04-22) |
Re: By value-result vs by reference andrewd@apanix.apana.org.au (1994-04-24) |
Re: By value-result vs by reference hbaker@netcom.com (1994-04-23) |
[6 later articles] |
Newsgroups: | comp.compilers |
From: | graham@pact.srf.ac.uk (Graham Matthews) |
Keywords: | design |
Organization: | University of Bristol, England |
Original-Sender: | usenet@bris.ac.uk (Usenet news owner) |
References: | 94-04-140 |
Date: | Thu, 21 Apr 1994 10:47:41 GMT |
Frederic Guerin (guerin@iro.umontreal.ca) wrote:
> I would like to hear about call-by-value-result vs call-by-reference,
> which one is better ?
> Most of the today popular languages have adopted the call-by-reference as
> a mean to pass variable arguments to procedure-function.
> [efficiency argument deleted]
The problem with this kind of discussion is that the semantics of the rest
of the language effect the discussion so much. Specifically a language may
have semantics such that the programmer can only use call by value, but
the implementation can implement everything using call by reference (a
language like Sisal comes to mind here). Whether one calling convention is
better than the other becomes pretty moot in this kind of set up.
graham
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.