Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: THROW codes and ambiguous conditions Date: Tue, 10 Jun 2025 14:11:30 -0700 Organization: A noiseless patient Spider Lines: 8 Message-ID: <878qlz47zx.fsf@nightsong.com> References: <87plff4938.fsf@nightsong.com> <87ldq33svl.fsf@nightsong.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Tue, 10 Jun 2025 23:11:31 +0200 (CEST) Injection-Info: dont-email.me; posting-host="139aba8ba34ab23e150973583f26b926"; logging-data="1576943"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Ucw62ERa8SyIyU2iswsoZ" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:fdjgM0jfNgl/OChJECRA8hse8PI= sha1:EZS3t48WOV/aT0OkHc0EFknulSo= albert@spenarnc.xs4all.nl writes: > Probably there is, revectoring EMIT and forcing the Forth to work > with single characters. Anton Ertl can show how it is done with > gforth. Yes, but it seems to be implementation specific. Reasonable point about <#... being in CORE. It always seemed to me that those words should have been in an extension.