Sujet : Re: nest-sys revisited
De : dxforth (at) *nospam* gmail.com (dxf)
Groupes : comp.lang.forthDate : 17. Mar 2025, 02:14:38
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <0a267120565f86b1be396616f06ae9c81e5043a6@i2pn2.org>
References : 1 2 3
User-Agent : Mozilla Thunderbird
On 17/03/2025 2:30 am, Hans Bezemer wrote:
On 14-03-2025 02:26, dxf wrote:
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.
I agree with most of what you say - except EXECUTE, a "function" can be called, but has to return *somewhere* - otherwise it is a BRANCH (jump).
Would you agree 'nest-sys' are peculiar to colon definitions. That
EXECUTE is a different class of function. It's not doing a 'call'
as such and not leaving anything on the 'return stack'?