Sujet : Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]
De : albert (at) *nospam* spenarnc.xs4all.nl
Groupes : comp.lang.forthDate : 29. Sep 2024, 13:40:58
Autres entêtes
Organisation : KPN B.V.
Message-ID : <nnd$5f2c6352$21f00518@b4f8091cb7661ebd>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
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 WallArt For Home, Office And Garden Decor - Perfect For Windows, Bars,And Gifts For Friends Family And Colleagues.