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) |
Re: By value-result vs by reference nebbe@lglsun.epfl.ch (1994-04-26) |
Re: By value-result vs by reference Theo.Norvell@comlab.oxford.ac.uk (1994-04-26) |
Re: By value-result vs by reference hbaker@netcom.com (1994-04-28) |
[3 later articles] |
Newsgroups: | comp.compilers |
From: | Dik.Winter@cwi.nl (Dik T. Winter) |
Keywords: | design |
Organization: | CWI, Amsterdam |
References: | 94-04-140 |
Date: | Thu, 21 Apr 1994 22:49:58 GMT |
guerin@iro.umontreal.ca (Frederic Guerin) writes:
> Is there some good reason to prohibit call-by-value-result that I can't see,
> or is it coincidental of these days ?
>
In languages that do not prohibit aliasing call-by-value-result is wrong
in many cases. I.e. the body of a routine can access a variable through
its ref parameter, but also by other means (globals, other indirections,
etc.).
--
dik t. winter, cwi, kruislaan 413, 1098 sj amsterdam, nederland, +31205924098
home: bovenover 215, 1025 jn amsterdam, nederland; e-mail: dik@cwi.nl
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.