Path: csiph.com!aioe.org!.POSTED!not-for-mail From: Rod Pemberton Newsgroups: comp.lang.forth Subject: Re: TO implementation Date: Sun, 15 Jan 2017 22:19:01 -0500 Organization: Aioe.org NNTP Server Lines: 18 Message-ID: <20170115221901.6a57e261@_> References: <9ec202ed-8f32-4b76-b1a2-3cfaafbed507@googlegroups.com> <2017Jan7.150224@mips.complang.tuwien.ac.at> <2017Jan8.162730@mips.complang.tuwien.ac.at> <2017Jan9.192014@mips.complang.tuwien.ac.at> <2017Jan15.161523@mips.complang.tuwien.ac.at> NNTP-Posting-Host: n4wpt9zq8xR26Ttf9mo2BA.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Claws Mail 3.13.1 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) Xref: csiph.com comp.lang.forth:54052 On Sun, 15 Jan 2017 13:34:47 -0600 Andrew Haley wrote: > STATE sucks. So do all mechanisms which cause words to behave > differently depending on whether they are called by the interpeter or > the compiler. I think I have been fairly consistent about this. Yet, STATE is CORE and required for certain words: http://forth-standard.org/standard/core/STATE STATE seems to be required for the recently discussed SYNONYM too, at least in the online version of the standard which provides an implementation of SYNONYM using STATE: http://forth-standard.org/standard/tools/SYNONYM Rod Pemberton