Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!gatech!mcdchg!clyde!feg
From: feg@clyde.ATT.COM (Forrest Gehrke)
Newsgroups: comp.lang.c
Subject: Re: return(struct) implementation
Summary: Invisible parameter?
Message-ID: <42110@clyde.ATT.COM>
Date: 9 Mar 89 16:07:53 GMT
References: <4425@pt.cs.cmu.edu> <1989Mar7.163952.20063@utzoo.uucp>
Organization: AT&T Bell Labs, Whippany NJ
Lines: 18

In article <1989Mar7.163952.20063@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
.>  [.....deletes] 
> Just about every permutation of putting it on the stack is probably
> in use in some compiler or other.  Probably the best approach, although
> it's one that requires correct declaration, is to have the caller pass
> in a pointer (as an invisible extra parameter) to where he wants the
> return value put.  Even stranger approaches have been used in some
.>  [deletes]




I don't understand how a programmer calls a function and passes
an "invisible extra parameter".  What device does he use to
accomplish this? .....Or, are you talking about the compiler
programmer?

Forrest Gehrke