Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!news.quux.org!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail
From: mhx@iae.nl (mhx)
Newsgroups: comp.lang.forth
Subject: Re: How robust is INCLUDE
Date: Fri, 20 Dec 2024 11:23:43 +0000
Organization: novaBBS
Message-ID: <b8a962692f028f2d5b4eb05b18f3979f@www.novabbs.com>
References: <e2087f81f803be03f7b87c51f0e4cc8a@www.novabbs.com> <1390f68a27da2755ed77ea113cb7243d@www.novabbs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="3771138"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="J+nubxJRM7ncpF4l6KLO+OONWmFAYJHVJegfwQXJ8vc";
User-Agent: Rocksolid Light
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Posting-User: 4e0dc1fdad1ead10b39e7eb5db19bf73d73e3ab3
X-Rslight-Site: $2y$10$w5dLi7oK3YdyQDJ5EbkAFeNTeJqu.XAy1pj461EB8BVB0e4dRV.mC

On Fri, 20 Dec 2024 10:12:13 +0000, minforth wrote:

> I don't think I quite understand what you're trying to achieve.
> But what happens if there are errors in the process?
> Leftover garbage on the s-stack?

In iForth the S-stack is a first class citizen. It might also work
to make this stack cyclical.

> At least in my system(s), INCLUDED is implemented with an
> internal CATCH/THROW mechanism, which clears all important
> stacks (and some internal stuff) on error.

I would sure hope so :-)

> As for ANS compatibility: who cares, as long as your code
> is well documented.

I was more interested in WHY it would not be compatible.
In (old) SwiftForth the problem is that >R and R> don't work while
INCLUDEing. In (very old) gForth the problem is compiler
security. The [ >S ] is supposed to move the expected address
left by :NONAME away to expose the arguments on the data
stack. In gForth the data stack is polluted with security stuff.

Was there a problem in minforth?

-marcel