Date: Wed, 11 Sep 2024 12:03:05 +1000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Avoid treating the stack as an array [Re: "Back & Forth" is
 back!]
Newsgroups: comp.lang.forth
References: <nnd$61e0ad9a$48ed61c2@b4d945e456041481>
 <vasqjd$icjm$1@dont-email.me> <66d26c4b$1@news.ausics.net>
 <vaubf7$tbke$1@dont-email.me> <nnd$04cff141$0193ba04@301336b8dd8ed69a>
 <vbfqnd$v4c4$1@dont-email.me> <nnd$26b4d59b$27bdb181@ce638e508b04426e>
 <87bk0vbvgk.fsf@nightsong.com>
Content-Language: en-GB
From: dxf <dxforth@gmail.com>
In-Reply-To: <87bk0vbvgk.fsf@nightsong.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: news.ausics.net
Message-ID: <66e0fa58$1@news.ausics.net>
Organization: Ausics - https://newsgroups.ausics.net
Lines: 14
X-Complaints: abuse@ausics.net
Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!news.ausics.net!not-for-mail
Bytes: 1667

On 10/09/2024 9:26 pm, Paul Rubin wrote:
> Hans Bezemer <the.beez.speaks@gmail.com> writes:
>> What bothers me most technologically is that parameters flow through
>> the stack undisturbed. You break that paradigm when using locals. With 
>> locals you *HAVE TO* create some kind of stack frame that you have to
>> destroy when you exit.
> 
> Forth programs very frequently end up juggling parameters and other data
> to and from the return stack, instead of using locals.

Looking at an application with 154 colon definitions, only 2 were found
to use the return stack for temporary storage.  Even I was surprised :)