Path: csiph.com!aioe.org!.POSTED!not-for-mail From: Rod Pemberton Newsgroups: comp.lang.forth Subject: Re: Make Forth Small Again! Date: Thu, 23 Mar 2017 00:57:42 -0400 Organization: Aioe.org NNTP Server Lines: 26 Message-ID: <20170323005742.1e342c5a@_> References: <87pohbhmxc.fsf@nightsong.com> <380124c4-7591-4c55-a262-3d92b5bd4333@googlegroups.com> <2017Mar21.174630@mips.complang.tuwien.ac.at> <2017Mar22.141045@mips.complang.tuwien.ac.at> NNTP-Posting-Host: ZTD62cW/Uw8bymX5ok+0NA.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 Xref: csiph.com comp.lang.forth:56158 On Wed, 22 Mar 2017 07:43:26 -0700 (PDT) hughaguilar96@gmail.com wrote: > On Wednesday, March 22, 2017 at 6:13:59 AM UTC-7, Anton Ertl wrote: > When QUIT executes (typically when ABORT or ABORT" call it), QUIT > fails to restore the system to a known state. 1.) BASE still has the > value that it had prior to the abort. 2.) The search-order is the > same as it was prior to the abort. 3.) The current word-list is the > same as it was prior to the abort. ... > The intelligent design for a Forth system would be for QUIT to > restore global variables (such as BASE the search-order, etc.) that > describe the state of the Forth system. Since QUIT is usually the first word executed, why wouldn't QUIT do this already? Rod Pemberton -- All it takes for humanity to conquer the world's toughest problems is to hope, to believe, to share, and to do, in cooperation.