Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: How does the input stream traditionally work?
Date: Mon, 16 Mar 2026 15:14:33 -0700
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <87jyvbcth2.fsf@nightsong.com>
References: <87bjgre5yy.fsf@nightsong.com> <2026Mar14.122649@mips.complang.tuwien.ac.at> <871phleh3v.fsf@nightsong.com> <69b65f35$1@news.ausics.net> <87wlzcdesv.fsf@nightsong.com> <69b744ec@news.ausics.net> <87o6kod1h3.fsf@nightsong.com> <69b76740$1@news.ausics.net>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Mon, 16 Mar 2026 22:14:34 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="339b8262cc1958fd1f442376bac3558f"; logging-data="2518809"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/jGbYJ2VMC5QE5mlXcUubD"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:Z33ZlsLS1QhNJ5+7siXu0/TFYvU= sha1:6dSLYjOFquLbG47n+e6kkQI4bOg=
Xref: csiph.com comp.lang.forth:134709

dxf <dxforth@gmail.com> writes:
> For each nest there's state stuff that needs saving (loadline# source
>>in blk etc).

Oh I had figured that would be in the FDB.  Does it have to be on the
stack for some reason?

> Then there's RS usage incurred during load/compile of the current
> file.  It all adds up.

I wonder if moving the state to the FDB can get rid of the need for
stack nesting.  Then it's just a matter of how many FDB's you want to
set aside space for.  You could even put them in the ALLOCATE heap if
you have that.