Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Coroutines in Forth Date: Wed, 22 Apr 2026 11:18:33 -0700 Organization: A noiseless patient Spider Lines: 15 Message-ID: <871pg66epy.fsf@nightsong.com> References: <10qunhm$1nnbt$1@dont-email.me> <10r1825$2d8j6$1@dont-email.me> <69db0856$1@news.ausics.net> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Wed, 22 Apr 2026 18:18:33 +0000 (UTC) Injection-Info: dont-email.me; posting-host="a5f2eb70ea72c76b516e0a292728a832"; logging-data="2583802"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/mmEETl6/rCXDfWsdcBSTk" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:Eew4sGXduCRmzcAxd9VYa5ReZl8= sha1:oy+j+3Ri0E177Ka8h3g2e2/9jkY= Xref: csiph.com comp.lang.forth:134943 dxf writes: > IMO local variables in forth was less about 'stack juggling' than > simulating the 'look and feel' code of other languages. Forth locals > code uses a fair number of TO's. Hugh once suggested locals ought to > have used @ ! . This would have been very forth-like - but completely > misses what locals aficionados were trying to do! When I've used locals it's been to avoid contortions reaching into the stack, including the floating point stack, where FPICK is non-standard. There's also the realization that computer memory except for a few specialized Forth chips is always made from RAM. So ideological devotion to a pure stack VM seems to pass up perfectly good hardware capabilities. Gforth does support address-like locals if you want to use them.