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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fd63afa4dc364b7e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-03-17 01:38:53 PST Path: nntp.stanford.edu!newsfeed.stanford.edu!news.tele.dk!212.54.64.131!news100.image.dk!feed.news.nacamar.de!news.fh-hannover.de!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Better support for garbage collection Date: 15 Mar 2001 17:36:55 +0100 Organization: Enyo's not your organization Message-ID: <87pufjkmzc.fsf@deneb.enyo.de> References: <98m938$2iod0$1@ID-25716.news.dfncis.de> <87bsr46kxv.fsf@deneb.enyo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Xref: nntp.stanford.edu comp.lang.ada:91485 Date: 2001-03-15T17:36:55+01:00 List-Id: Robert A Duff writes: > Florian Weimer writes: > > > This is solved by double indirection. Access values are not > > addresses, but opaque handles. The compiler is expected to lock the > > handle to obtain the actual address. > > Ah, so it's sort of like the original implementation of Smalltalk-80 -- > an array of addresses of "instances", and a pointer to an instance > actually contains the array index? I don't know about Smalltalk-80, but the same scheme was implemented on Windows 2.x and 3.x. Of course, with the advent of the 286 and especially the 386 and virtual memory management, nobody bothered to unlock the local or global heap anymore.