From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e5eb8ca5dcea2827
X-Google-Attributes: gid103376,public
From: Hyman Rosen <hymie@prolifics.com>
Subject: Re: Ada OO Mechanism
Date: 1999/06/08
Message-ID: <t7ogiqz8e3.fsf@calumny.jyacc.com>#1/1
X-Deja-AN: 487235383
Sender: hymie@calumny.jyacc.com
References: <7i05aq$rgl$1@news.orbitworld.net> <374AC676.F7AE0772@lmco.com>
 <t7iu9hrqpw.fsf@calumny.jyacc.com> <7ieuja$5v9@news1.newsguy.com>
 <t7675gswiv.fsf@calumny.jyacc.com> <7ifd6l$bmf@sjx-ixn1.ix.netcom.com>
 <t7zp2sr6yf.fsf@calumny.jyacc.com> <uvhdfzpgn.fsf@infomatch.com>
 <7ihf6i$4hv@dfw-ixnews10.ix.netcom.com> <t7k8tvqyjr.fsf@calumny.jyacc.com>
 <m3909y7bar.fsf@mheaney.ni.net> <t7wvxfn75v.fsf@calumny.jyacc.com>
 <m3emjnh660.fsf@mheaney.ni.net> <t7emjmmx8w.fsf@calumny.jyacc.com>
 <7jjpru$2t1b@news2.newsguy.com>
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@panix.com
X-Trace: news.panix.com 928877384 25818 209.49.126.226 (8 Jun 1999 21:29:44
 GMT)
Organization: PANIX Public Access Internet and UNIX, NYC
Mime-Version: 1.0
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3
NNTP-Posting-Date: 8 Jun 1999 21:29:44 GMT
Newsgroups: comp.lang.ada
Date: 1999-06-08T21:29:44+00:00
List-Id: <comp.lang.ada>

Samuel Mize <smize@imagin.net> writes:
> I should say, of course, that O is allocated on stack on typical
> architectures, by typical compilers.

Yes, of course. I am trying to understand the mechanism behind T'Class
variables on ordinary architectures.

> O is allocated on stack, just like any other declare-block variable.
> (A function/procedure local variable would be just the same.)
> O's size is determined at run-time, when it finds out exactly what
> type of object it has to hold.

So where does the returned value from the function live between the
time the function returns and the time space is allocated on the stack
for O?