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: Sun, 15 Mar 2026 13:21:36 -0700
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <87wlzcdesv.fsf@nightsong.com>
References: <87bjgre5yy.fsf@nightsong.com> <2026Mar14.122649@mips.complang.tuwien.ac.at> <871phleh3v.fsf@nightsong.com> <69b65f35$1@news.ausics.net>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Sun, 15 Mar 2026 20:21:37 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="a6fccd628ca27a36ab5196c8bd928039"; logging-data="1468428"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/W674MVwu6LXnGXAWOagmQ"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:K7bLi/pjpP1ZoNTKIMH4nGTA6XY= sha1:3X5PwW63dJPqlD8yFjAyZMwn+Zc=
Xref: csiph.com comp.lang.forth:134687

dxf <dxforth@gmail.com> writes:
> DX-Forth uses a 256 byte return stack.  The consequence of that is only
> about 6 files can be included before it runs out.  

If you mean 6 levels of nesting, that seems sufficient for a small
system.  It's around 20 return stack cells for each level.  Is that for
a blocks system, or do you have files?  I guess it's reasonable to set
aside a chunk of dictionary or block space to use as an explicit stack,
if you want to remember filenames.

Do you use RPICK or anything like that, to get at the data for the
current level?  

I still don't understand the issue with using the data stack.  Maybe I
haven't thought about it enough.