v4 fabric to spec: the mesh boot, the one adaptive heartbeat, mechanism A (#189) #197

Merged
rajames merged 160 commits from StarForth-v4.0.0 into master 2026-11-19 11:19:50 +00:00
Showing only changes of commit 1f128df5df - Show all commits
+7
View File
@@ -98,3 +98,10 @@ What they are:
says (kind 4: 29 cases), v4 is held to the table -- what v3 meant -- and each such case is listed. Where a
case's output names v3's internals (kind 3), v4 is held to the same form with its own words: the case's
shape, v4's values; listed too. Everything else: v3's recorded behaviour, exactly.
**Ruled (Captain Bob, 2026-11-14): "The standard first".** Read with their descriptions, v3's cases are not a
reliable authority: `16 BASE ! 255 .` -- v3 prints 597, its description says FF, FORTH (and v4) print 255; `M+`
-- v3 300 0, its description 200 100, FORTH and v4 100 200. So, for each case: FORTH-79 where it defines the
word (as `post79_rules.py` already does for the Required set); FORTH-83 for words 79 lacks (`M+`, `2>R` ...);
v3's behaviour -- or its table, where v3 contradicts it -- only for v3's own extensions no standard defines
(`COMPARE`'s form, `ENTROPY@`, `TOP-WORDS` ...). Every case rewritten is listed with its reason.