Re: kForth-32 v 2.7.0

From	thresh3@fastmail.com (Lev)
Newsgroups	comp.lang.forth
Subject	Re: kForth-32 v 2.7.0
Date	2026-03-19 17:54 +0000
Organization	A noiseless patient Spider
Message-ID	<10phd8n$u16a$1@dont-email.me> (permalink)
References	<10phc30$tj97$1@dont-email.me>

Show all headers | View raw

Krishna Myneni <krishna.myneni@ccreweb.org> wrote:

> This update of kForth-32 (v 2.7.0) mirrors recent substantial
> changes to kForth-64, in particular to the interpreter/compiler
> which has been rewritten to align with the recognizers proposal
> for the Forth 202x standard.

How much did the rewrite change your text interpreter?  The
recognizer proposal essentially factors what was a monolithic
INTERPRET into a chain of recognizers -- rec-name, rec-number,
etc. -- each returning a typed translation.

I'm curious whether you found this made things cleaner in
practice or just moved the complexity around.  The proposal
defines translate: for building new recognizer types, which
seems like it could open up things like recognizing hex
literals with 0x prefix or string literals inline, without
touching the core interpreter.  Have you experimented with
custom recognizers beyond the standard set?

Also -- integrated data/fp stack is unusual.  What drove that
design choice over separate stacks?

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

kForth-32 v 2.7.0 Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-19 12:34 -0500
  Re: kForth-32 v 2.7.0 Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-19 12:37 -0500
  Re: kForth-32 v 2.7.0 thresh3@fastmail.com (Lev) - 2026-03-19 17:54 +0000
    Re: kForth-32 v 2.7.0 Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-19 20:45 -0500
  Re: kForth-32 v 2.7.0 Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-12 10:25 -0500
    Re: kForth-32 v 2.7.0 Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-05-17 17:53 -0500

csiph-web