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: RfD Recognizer, 3rd version
Date: Mon, 26 Sep 2016 21:39:45 -0700
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <87oa3a6jn2.fsf@jester.gateway.pace.com>
References: <e0f59404-13f6-4d65-8519-db51484569be@googlegroups.com> <a6a3672d-2e36-4085-93bf-fbf4cc3a7d0e@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="2aed369a7b4699bde3e169ff4d831123"; logging-data="28485"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/XGhFlvmkY9/JaNoJlyS8I"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:OfdRjx/RDzdNvJdbTzPWCh2kNcQ= sha1:m+is10NdbNZPheAlF8vtS5nmiwo=
Xref: csiph.com comp.lang.forth:51356

trans <transfire@gmail.com> writes:
> Could someone explain how recognizers work in laymen terms?

After parsing a word, pass it to a series of user-supplied functions
(plus some default ones) until one of them decides that it knows how to
handle the word.  This contrasts with the traditional system of having
special hair built into the text interpreter to handle things like
numeric literals, char constants in 'x' notation, etc.