Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!apple!dlyons
From: dlyons@Apple.COM (David Lyons)
Newsgroups: comp.lang.forth
Subject: Re: Forth Implementation Question
Keywords: Forth, 68000
Message-ID: <34741@apple.Apple.COM>
Date: 15 Sep 89 00:01:29 GMT
References: <1715@thumper.bellcore.com> <7972@medusa.cs.purdue.edu> <17623@bellcore.bellcore.com>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 25

In article <17623@bellcore.bellcore.com> sdh@wind.UUCP (Stephen D Hawley) writes:
>In article <7972@medusa.cs.purdue.edu> bouma@cs.purdue.EDU (William J. Bouma) writes:
>[...]  You have to write a garbage collector.

Not necessarily--the host system may already have one as part of its memory
management routines.  (For forgetting a single word, this would mean having
each word in its own memory block, & possibly using something more complicated
than pointers for most operations.  Handles, for example.)

>[...]
>Forth is dangerous in a machine that does not have memory protection [...]

Gee...*anything* is dangerous in a machine that doesn't have memory
protection.  I spend a large amount of time tracking down "Who stomped on
*that* byte?" problems (mostly on the Apple IIgs--in my programs and other
people's), and the source is usually assembly, Pascal, or C.
-- 

 --Dave Lyons, Apple Computer, Inc.          |   DAL Systems
   AppleLink--Apple Edition: DAVE.LYONS      |   P.O. Box 875
   AppleLink--Personal Edition: Dave Lyons   |   Cupertino, CA 95015-0875
   GEnie: D.LYONS2 or DAVE.LYONS         CompuServe: 72177,3233
   Internet/BITNET:  dlyons@apple.com    UUCP:  ...!ames!apple!dlyons

   My opinions are my own, not Apple's.