Deutsch   English   Français   Italiano  
<nnd$3a616a68$735d3805@123d8a188c4e0435>

View for Bookmarking (what is this?)
Look up another Usenet article

Date: Fri, 10 Jan 2025 13:42:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: "Back & Forth" - Local variables
Newsgroups: comp.lang.forth
References: <nnd$75b7a2a4$616fdd6b@4f60b314ce95c9b9>
 <nnd$65a6d402$1bfbf0ca@d49afc2a32e40cf2>
 <752c8e210166d00119336309dc35240d36d6f17d@i2pn2.org>
 <9747ef2be5ee93d6a4f0c89352a38cec72624609@i2pn2.org>
 <nnd$43da5afe$0d359236@662b3066f040a86b>
 <6a2d3e50f9435ebced9e72d5770af8ff75b6153e@i2pn2.org>
 <nnd$44fc771d$089c856c@db10b46852f85b89>
 <7f4d1c07f94e604c28d4f13ee6b7ecbe8138c28d@i2pn2.org>
Content-Language: en-US
From: Hans Bezemer <the.beez.speaks@gmail.com>
In-Reply-To: <7f4d1c07f94e604c28d4f13ee6b7ecbe8138c28d@i2pn2.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <nnd$3a616a68$735d3805@123d8a188c4e0435>
Organization: KPN B.V.
Path: ...!eternal-september.org!feeder3.eternal-september.org!2.eu.feeder.erje.net!feeder.erje.net!feeder1.feed.ams11.usenet.farm!feed.usenet.farm!feed.abavia.com!abe007.abavia.com!abp002.abavia.com!news.kpn.nl!not-for-mail
Lines: 26
Injection-Date: Fri, 10 Jan 2025 13:42:56 +0100
Injection-Info: news.kpn.nl; mail-complaints-to="abuse@kpn.com"
Bytes: 2388

On 10-01-2025 00:54, dxf wrote:
> The >R dependency is on what was (and perhaps still is) 'common practice'.
> I was unsure how it would fare but all the popular forths seem to work.
> If ANS-FORTH has issued one too many 'Thou shalt not's and in doing so has
> excluded itself then that's too bad.

Oh, you won't find me on the side of "the standard". As a matter of 
fact, 4tH allows a lot of things that the standard doesn't allow and 
vice versa. But I think it is a useful tool when deciding what SHOULD be 
portable or SHOULDN'T be portable.

In general, I'm all for adopting "common practice" (I'm not going to 
list all my exceptions). In this case - why not?

1. It's very hard to enforce (unless you flag all RS items - ugly - or 
separate the call stack);
2. It's useful to create e.g. co-routines;
3. I don't recommend the practice, though. It's hard to wrap your head 
around and in 4tH it may clash with the tail call optimizer. But since 
4tH is completely sandboxed, you can't do much damage. If you (attempt 
to) jump outside the box, the program is halted.

Hans Bezemer