Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!news.cse.psu.edu!uwm.edu!cs.utexas.edu!howland.reston.ans.net!plug.news.pipex.net!pipex!tank.news.pipex.net!pipex!netcom.net.uk!ix.netcom.com!ix.netcom.com!ixnews1.ix.netcom.com!netcom.com!sehyo
From: sehyo@netcom.com (Sehyo Chang)
Subject: Re: Segmented memory
Message-ID: <sehyoDq0wJp.sC@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
X-Newsreader: TIN [version 1.2 PL1]
References: <4l34oa$nrs@crocus.gamma.ru>
Date: Wed, 17 Apr 1996 20:21:25 GMT
Lines: 19
Sender: sehyo@netcom20.netcom.com

visualage@ wrote:
: If I understand it properly, memory segments in Smalltalk
: object memory system were introduced just because of
: the size of the addressable space on original machines 
: original Smalltalk was developed for. I see, however, we
: didn't get rid of this ST OM model yet, so I suspect it's
: something more behind this. Can anyone explain me how
: use of Smalltalk Object Memory segments is judjed today?

: Thanks,

: Boris G. Shingarov

The current VM implementation does not use segmented architecture
at least far as I know. All 32-bit VM uses direct pointer instead of
indirect object pointers. For some of the historical background, read:
"Smalltalk-80 bits of history, words of adivce: by Gleen Krasner". 

-- sehyo

