Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.lang.forth
Subject: Re: Toy Forth (memory management)
Message-ID: <6331@tekgvs.LABS.TEK.COM>
Date: 10 Nov 89 23:09:35 GMT
References: <8538@medusa.cs.purdue.edu> <918@acf5.NYU.EDU> <8612@medusa.cs.purdue.edu>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 15

This may sound crazy, but anyone interested in a dynamic memory managed
Forth should look at Smalltalk (particularly the book "Smalltalk-80 The
Language and It's Implementation"). Once you clear away the window dressing
(pun intended) you find a token thread interpreted stack machine with
dynamic memory management of objects (and *everything* in Smalltalk is an
object).

I spent a year of my life porting Smalltalk-80 to an 80386 and the whole time
I felt like I was working on a bloated Forth (The "kernel", consisting of
the interpreter with its primitives is >64k, but the code threads are very
compact -- more so than Forth).

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply