Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: Make Forth Small Again!
Date: Sat, 01 Apr 2017 09:23:40 -0700
Organization: A noiseless patient Spider
Lines: 7
Message-ID: <87zig05c6r.fsf@nightsong.com>
References: <b78c6e56-758d-475e-8973-d0e4a9112105@googlegroups.com> <b2e57f69-68ec-427d-aa1d-a991a5537f32@googlegroups.com> <ob2qhv$it1$1@dont-email.me> <30c31c0b-2973-4ddf-9f02-4b0807c76c11@googlegroups.com> <ob3b1g$c1s$1@dont-email.me> <5f7166de-1d39-444e-8eb3-a86e581c63b1@googlegroups.com> <ob6t6s$5id$1@dont-email.me> <9eb7f6df-c5fe-4152-8460-4600b3d4747b@googlegroups.com> <ob7rmv$1pv$1@dont-email.me> <af28d6f2-f151-438d-a1c5-9485f79b41a4@googlegroups.com> <obb7jb$r5a$1@dont-email.me> <1dc31777-68ed-4c2b-a366-442abb54d940@googlegroups.com> <9a17aa4f-cdcc-4e43-91d9-262e40ad91cc@googlegroups.com> <6dbe3c9c-73ab-4143-a21b-ca35c633fd57@googlegroups.com> <f5807046-6fc1-43e5-be4b-33a91a4b6347@googlegroups.com> <94859086-568f-462d-9aa0-ac95d52a8e33@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="ff26b854902ce90675a6827320cb0fd1"; logging-data="26333"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18S+8YWYMNvmJ85+US9gYKg"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:vD+1/opb+xySTW99g8fA7xUlJuE= sha1:zvkNF5LcaVyEB6me0sYN0kwTILU=
Xref: csiph.com comp.lang.forth:56543

Mark Wills <markwills1970@gmail.com> writes:
> Agree. I'd even go so far as to advocate a control stack so that the
> return stack can be used if necessary inside loops.

Wait, what?  You want a separate stack for loop indices?  Ok, but why
not put the return address there too, so the formerly return stack would
be available for arbitrary user data?