Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucdavis!egg-id!ui3!dickow
From: dickow@ui3.UUCP
Newsgroups: comp.lang.forth
Subject: Re: other forth applications
Message-ID: <34240002@ui3.UUCP>
Date: 31 Jan 90 07:31:41 GMT
References: <345.UUL1.3#5129@willett.UUCP>
Organization: MRC, University of Idaho
Lines: 13

>/ ui3:comp.lang.forth / ForthNet@willett.UUCP (ForthNet articles from GEnie) /  4:52 pm  Jan 25, 1990 /
>W.BADEN1 [Wil]               at 18:55 PST
>Forth enlightenment:  The  principal input method in Forth is not KEY or
>EXPECT, but  INTERPRET.  

   Yeah, that's the ideal, but quite a few forth systems can not be
distributed freely without disabling the interpreter, scrambling the
dictionary names, etc. Often you have to write a pseudo-interpreter then
to call your application words.

Bob Dickow (...egg-id!ui3!dickow)
           (rdickow@groucho.mrc.uidaho.edu)
           (dickow@idui1.bitnet)