Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Is there a free version of Forth that uses the exact same words Date: Mon, 10 Apr 2017 12:27:24 -0700 Organization: A noiseless patient Spider Lines: 12 Message-ID: <87pogk6p2b.fsf@nightsong.com> References: <2017Apr8.163050@mips.complang.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="a3cff8cb11164143d7656bbe7803b502"; logging-data="7841"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/KeRKBys/Vz9Np95CRpsxa" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:B+KAb7SfLRaVF/a4iFEOxQ7HHw0= sha1:j/rnlgz7gsbAvu0zxDlERq+tICM= Xref: csiph.com comp.lang.forth:57013 "Elizabeth D. Rather" writes: > IMO understanding Forth implementation strategies is a diversion from > the objective of learning how to use it in *applications*, which is > its purpose. It seems to me that a lot of Forth's design is driven by enabling the implementation of Forth in Forth. That is, Forth *is* a Forth application, maybe even an archetypal application. I've found eForth (Bill Muench's original version, not one of the ports) to be the most enlightening and understandable Forth implementations that I've looked at so far.