Path: ...!news.misty.com!weretis.net!feeder9.news.weretis.net!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail
From: minforth@gmx.net (minforth)
Newsgroups: comp.lang.forth
Subject: Re: Lispification of Forth
Date: Tue, 27 May 2025 20:23:02 +0000
Organization: novaBBS
Message-ID: <d02785598e82c63663532d84d40de0f7@www.novabbs.com>
References: <nnd$5626862c$3b1b09a0@e3b20ce8a9e1d1e9>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="2187371"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="BZ29EnRIXfdX99fE+pfHgueF2xuF1KvSpLJsfuOZy3Y";
User-Agent: Rocksolid Light
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Site: $2y$10$bn1/U29.iJ8tgc6VDRQnm.NbpWLyrojE1kXvGUXpCZ1EyrywsmBp.
X-Rslight-Posting-User: 0338a3da6f3e9c9f1401b365bcd9c3ed8de2227a
Bytes: 1247
Lines: 7

It might be less complicated to use tokens or hashes
instead of memory addresses in high-level Forth code.
All dictionaries, data or VM code sequences could then
be localised exclusively via a central token table or
hash table. Replacing/modifying a word would be very
simple by patching the token/hash table.

--