Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!MITCH.ENG.SUN.COM!wmb
From: wmb@MITCH.ENG.SUN.COM
Newsgroups: comp.lang.forth
Subject: Separation of code and data space
Message-ID: <9008230615.AA28602@ucbvax.Berkeley.EDU>
Date: 21 Aug 90 16:06:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: wmb%MITCH.ENG.SUN.COM@SCFVM.GSFC.NASA.GOV
Organization: The Internet
Lines: 13

> Second, I think that the requirement for separate dictionary and code
> spaces is overly restrictive and unnecessary.

It can be awfully handy for several environments:

a) ROM/RAM systems.
b) "Harvard architectures" with separate code and data storage
c) Turnkey applications where you may want to selectively remove
   headers.
d) Brain-damaged segmented architectures like the one that F-PC
   has to run on.

Mitch