Path: ...!eternal-september.org!feeder3.eternal-september.org!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: dxf <dxforth@gmail.com>
Newsgroups: comp.lang.forth
Subject: Re: nest-sys revisited
Date: Fri, 14 Mar 2025 12:26:56 +1100
Organization: i2pn2 (i2pn.org)
Message-ID: <8d760e814c0d0342eb9beaa0d271a6f1d1271e3a@i2pn2.org>
References: <nnd$451a798f$08238180@7ebfa2c34bfc24b8>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 14 Mar 2025 01:27:00 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="73500"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="XPw7UV90Iy7EOhY4YuUXhpdoEf5Vz7K+BsxA/Cx8bVc";
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
In-Reply-To: <nnd$451a798f$08238180@7ebfa2c34bfc24b8>
X-Spam-Checker-Version: SpamAssassin 4.0.0
Bytes: 1464
Lines: 12

On 14/03/2025 3:19 am, albert@spenarnc.xs4all.nl wrote:
> Apologize, for bad mouthing nested-sys in the coroutine discussion.
> (not that I like this concept).
> 
> In the ISO 94 document the concept of nest-sys is indeed needed.
> ...

Unavoidable really.  Nesting aka subroutine call - the process of
calling a function and when it completes, returning to the caller -
is a basic computing concept.  In forth 'nest-sys' represents the
information necessary to facilitate that return.  It should not be
confused with invoking a function i.e. 'xt' EXECUTE.