Sujet : Re: What with `` BL WORD ''
De : albert (at) *nospam* spenarnc.xs4all.nl
Groupes : comp.lang.forthDate : 16. Dec 2024, 11:42:44
Autres entêtes
Organisation : KPN B.V.
Message-ID : <nnd$4d7ec84e$49df8bc1@16bee34ce0a8759f>
References : 1 2
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
2024Dec15.170833@mips.complang.tuwien.ac.at>,
Anton Ertl <
anton@mips.complang.tuwien.ac.at> wrote:
albert@spenarnc.xs4all.nl writes:
In view of Gigabyte memories, a lot of interference could also be
avoided, if BL WORD were entitled to ALLOT the space.
A permanent region could serve as a transient region, so
from the users of WORD there is no problem.
>
: WORD WORD DUP COUNT ALLOT ALIGN ; \ Or some such.
>
Is this in conflict with the standard?
>
Yes. In
>
create foo bl word bar drop 1234 ,
foo @ .
>
the standard specifies that this prints "1234", but with your
redefinition of WORD, it does not.
>
More formally, the standard specifies that the memory allocated by ,
is contiguous with the data space of FOO, and WORD is not one of the
words that terminates a contiguous region.
Thanks. So if you are worried about transient storage interfering with
each other, the solution is to have a static buffer reserved for WORD.
I'll do that.
>
- anton
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.