Newsgroups: comp.lang.forth
References: <nnd$61e0ad9a$48ed61c2@b4d945e456041481> <87zfo4zps8.fsf@nightsong.com> <66eba538$1@news.ausics.net> <87h69zcxlh.fsf@nightsong.com>
From: albert@spenarnc.xs4all.nl
Subject: Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: albert@cherry.(none) (albert)
Message-ID: <nnd$5f2c6352$21f00518@b4f8091cb7661ebd>
Organization: KPN B.V.
Date: Sun, 29 Sep 2024 14:40:58 +0200
Path: ...!weretis.net!feeder8.news.weretis.net!2.eu.feeder.erje.net!feeder.erje.net!feeder2.feed.ams11.usenet.farm!feed.usenet.farm!feed.abavia.com!abe004.abavia.com!abp003.abavia.com!news.kpn.nl!not-for-mail
Lines: 22
Injection-Date: Sun, 29 Sep 2024 14:40:58 +0200
Injection-Info: news.kpn.nl; mail-complaints-to="abuse@kpn.com"
Bytes: 1865

In article <87h69zcxlh.fsf@nightsong.com>,
Paul Rubin  <no.email@nospam.invalid> wrote:
<SNIP>
>What I'm unclear about is what the philosophical purist path has to say
>about optimizing compilers.  I think anyone wanting to reject locals for
>reasons of code efficiency, probably should be using a VFX-style
>compiler.  My own idea of purity says to use a simple interpreter and
>accept the speed penalty, using CODE when needed.

Maybe I'm a purist. Indirect threaded code is a clear expression
of programmers intent. That is the ideal foundation on which to
build optimisers. The only requirement for an optimiser is that
the results are the same. The program can be shorter or faster.
Locals are a hindrance.

Groetjes Albert
-- 
Temu exploits Christians: (Disclaimer, only 10 apostles)
Last Supper Acrylic Suncatcher - 15Cm Round Stained Glass- Style Wall
Art For Home, Office And Garden Decor - Perfect For Windows, Bars,
And Gifts For Friends Family And Colleagues.