Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!tektronix!uw-beaver!tikal!sigma!roman
From: roman@sigma.UUCP (Bill Roman)
Newsgroups: comp.lang.forth
Subject: Re: Read tables in FORTH?
Message-ID: <1006@sigma.UUCP>
Date: Thu, 15-Jan-87 12:15:16 EST
Article-I.D.: sigma.1006
Posted: Thu Jan 15 12:15:16 1987
Date-Received: Fri, 16-Jan-87 22:46:39 EST
References: <315@esunix.UUCP>
Reply-To: roman@sigma.UUCP (Bill Roman)
Organization: Summation, Inc., Kirkland, WA
Lines: 13
Summary: think small

In article <315@esunix.UUCP> bpendlet@esunix.UUCP (Bob Pendleton) writes:
>Has anyone tried using a read table in FORTH?...
>A read table associates a procedure with each character in the character
>set. Every time a character is read the procedure associated with that
>character is executed. The actions of the FORTH scanner can be implemented
>by proper selection of the procedures associated with each character. Most
>characters would be associated with procedures that store the character in a
>buffer, the procedure associated with blank could look up the contents of
>the buffer in the symbol table....

When writing Forth, think small.  Go look at the definition of INTERPRET,
there's really not much to it.  Now write your own version that works the
way you want.  Don't go and hack complex generality into INTERPRET.