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: ciforth model
Date: Fri, 24 Apr 2026 10:38:34 -0700
Organization: A noiseless patient Spider
Lines: 5
Message-ID: <87se8k45t1.fsf@nightsong.com>
References: <nnd$2bd819ed$5423e023@908ce2ca63477284> <69e19091$1@news.ausics.net> <2026Apr17.092944@mips.complang.tuwien.ac.at> <nnd$112d8b41$6de5a871@c1c07004f259db9f>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Fri, 24 Apr 2026 17:38:35 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="08c798c78de11d74cf31823145047fd9"; logging-data="270827"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1++/cRLGNDRL6d079L6Vf5P"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:1LXdHlfLFBIwdPcX0KIiJ2R0o9Y= sha1:hvKxCultyHM/+oEsOFsGjO9E/DA=
Xref: csiph.com comp.lang.forth:134952

albert@spenarnc.xs4all.nl writes:
>  In this context a hash conflict is a redefinition. Avoid,

Unclear how to avoid, other than by storing the entire name so you can
detect the conflict.