Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,33 @@
|
||||
diff --git a/docs/v4.0.0/POST.md b/docs/v4.0.0/POST.md
|
||||
index 5c1ba7f9..1c4724a7 100644
|
||||
--- a/docs/v4.0.0/POST.md
|
||||
+++ b/docs/v4.0.0/POST.md
|
||||
@@ -67,7 +67,7 @@ standard's and not v3's.
|
||||
| `UPDATE.no_block` | `0 SCR ! UPDATE` | error | unchanged | stack `empty`, prints nothing | v3 raises an error FORTH-79 does not ask for |
|
||||
| `SCR.after_load` | `1 LOAD SCR @ . CR` | stack `empty`, printed `1 \n` | unchanged | stack `empty`, prints `1 \n` | v3 prints nothing after 1 LOAD; SCR is still 1 from the LIST before |
|
||||
| `FIND.existing` | `FIND DUP . CR` | stack `empty`, printed `7883424 \n` | unchanged | 0 value(s) left; output not compared | FORTH-79: FIND takes the next word, DUP here, and leaves its address, which is printed |
|
||||
-| `FIND.user_word` | `: test5 44 ; FIND test5 . CR` | stack `empty`, printed `8206544 \n` | unchanged | 0 value(s) left; output not compared | the address FIND leaves is printed |
|
||||
+| `FIND.user_word` | `: test5 44 ; FIND test5 . CR` | stack `empty`, printed `8206400 \n` | unchanged | 0 value(s) left; output not compared | the address FIND leaves is printed |
|
||||
| `FIND.empty` | `FIND` | error | unchanged | stack `0`, prints nothing | FORTH-79: FIND leaves 0 when there is no word; v3 raises an error |
|
||||
| `VOCABULARY.cross_vocab_access` | `VOCABULARY V1 V1 DEFINITIONS : V1WORD 11 ; FORTH V1WORD . CR` | stack `empty`, printed `11 \n` | unchanged | an error | FORTH-79: a word defined in another vocabulary is not found from FORTH; v3 finds it |
|
||||
| `VOCABULARY.duplicate` | `VOCABULARY TESTVOC VOCABULARY TESTVOC` | error | unchanged | stack `empty`, prints nothing | v3 raises an error FORTH-79 does not ask for: defining a name again |
|
||||
@@ -127,8 +127,8 @@ standard's and not v3's.
|
||||
| `LATEST.basic~2` | `LATEST @ . CR` | stack `empty`, printed `0 \n` | `LATEST 0<> . CR` | stack `empty`, prints `-1 \n` | v3's own word: v3 prints a value of its own machine (its DictEntry); the case as its description has it |
|
||||
| `LATEST.after_def` | `: test7 46 ; LATEST @ . CR` | stack `empty`, printed `0 \n` | `: test7 46 ; LATEST ' test7 = . CR` | stack `empty`, prints `-1 \n` | v3's own word: v3 prints a value of its own machine (its DictEntry); the case as its description has it |
|
||||
| `LATEST.after_forget` | `CREATE test8 FORGET test8 LATEST @ . CR` | stack `empty`, printed `0 \n` | `LATEST CREATE test8 FORGET test8 LATEST = . CR` | stack `empty`, prints `-1 \n` | v3's own word: v3 prints a value of its own machine (its DictEntry); the case as its description has it |
|
||||
-| `>BODY.basic` | `CREATE test9 ' test9 >BODY . CR` | stack `empty`, printed `8207624 \n` | `CREATE test9 FIND test9 >BODY ' test9 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
-| `>BODY.variable` | `VARIABLE var1 ' var1 >BODY . CR` | stack `empty`, printed `8208136 \n` | `VARIABLE var1 FIND var1 >BODY var1 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
+| `>BODY.basic` | `CREATE test9 ' test9 >BODY . CR` | stack `empty`, printed `8207480 \n` | `CREATE test9 FIND test9 >BODY ' test9 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
+| `>BODY.variable` | `VARIABLE var1 ' var1 >BODY . CR` | stack `empty`, printed `8207992 \n` | `VARIABLE var1 FIND var1 >BODY var1 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
| `ORDER.basic` | `ORDER` | stack `empty`, printed `Search order: (FIND)\nCurrent: (FIND)\n` | unchanged | stack `empty`, prints `Search order: FORTH \nCurrent: FORTH\n` | ANS Forth 16.6.2.1985 ORDER: the form is the system's; v3 names FORTH '(FIND)' -- v4's form with v4's names |
|
||||
| `ORDER.multiple` | `VOCABULARY TEST-VOC9 TEST-VOC9 DEFINITIONS ORDER` | stack `empty`, printed `Search order: TEST-VOC9 (FIND)\nCurrent:` | unchanged | stack `empty`, prints `Search order: TEST-VOC9 FORTH\nCurrent: TEST-VOC9\n` | ANS Forth 16.6.2.1985 ORDER: the form is the system's; v3 names FORTH '(FIND)' -- v4's form with v4's names |
|
||||
| `ORDER.after_forth` | `TEST-VOC9 FORTH ORDER` | stack `empty`, printed `Search order: (FIND)\nCurrent: (FIND)\n` | unchanged | stack `empty`, prints `Search order: FORTH \nCurrent: FORTH\n` | ANS Forth 16.6.2.1985 ORDER: the form is the system's; v3 names FORTH '(FIND)' -- v4's form with v4's names |
|
||||
@@ -141,7 +141,7 @@ standard's and not v3's.
|
||||
| `DECAY-RATE@.basic` | `DECAY-RATE@ . CR` | stack `empty`, printed `0 \n` | unchanged | stack `empty`, prints `1 \n` | v3's own word: the build's DECAY_RATE_PER_US_Q16, 1 by default (v3/Makefile, Kconfig.physics); the v3 that made the table was built with 0 |
|
||||
| `Q.VARIANCE.three_cells` | `100 HERE ! 200 HERE 8 + ! 300 HERE 16 + ! HERE 3 Q.VARIANCE Q.TO-INT . CR` | stack `empty`, printed `6666 \n` | `100 HERE ! 200 HERE 1 + ! 300 HERE 2 + ! HERE 3 Q.VARIANCE Q.TO-INT . CR` | stack `empty`, prints `6666 \n` | v3's address unit is a byte in 8-byte cells; v4's is a cell (D-1): the case in v4's units, a byte address 4 * a cell's |
|
||||
| `INFER-DECAY-SLOPE.three_cells` | `300 HERE ! 200 HERE 8 + ! 100 HERE 16 + ! HERE 3 INFER-DECAY-SLOPE Q.TO-INT . CR` | stack `empty`, printed `0 \n` | `300 HERE ! 200 HERE 1 + ! 100 HERE 2 + ! HERE 3 INFER-DECAY-SLOPE Q.TO-INT . CR` | stack `empty`, prints `0 \n` | v3's address unit is a byte in 8-byte cells; v4's is a cell (D-1): the case in v4's units, a byte address 4 * a cell's |
|
||||
-| `INFER-VARIANCE@.after_run` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT . CR` | stack `empty`, printed `39 \n` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT DROP CR` | stack `empty`, prints `\n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') |
|
||||
+| `INFER-VARIANCE@.after_run` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT . CR` | stack `empty`, printed `23 \n` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT DROP CR` | stack `empty`, prints `\n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') |
|
||||
| `INFER-WINDOW@.after_run` | `INFER-RUN INFER-WINDOW@ . CR` | stack `empty`, printed `0 \n` | `INFER-RUN INFER-WINDOW@ DROP CR` | stack `empty`, prints `\n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') |
|
||||
| `INFER-EARLY-EXIT@.after_run` | `INFER-RUN INFER-EARLY-EXIT@ . CR` | stack `empty`, printed `0 \n` | `INFER-RUN INFER-EARLY-EXIT@ DUP 0= SWAP 1 = OR . CR` | stack `empty`, prints `-1 \n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') (0 or 1) |
|
||||
| `Q.1.raw_value` | `Q.1 . CR` | stack `empty`, printed `65536 \n` | `Q.1 D. CR` | stack `empty`, prints `65536 \n` | Q48.16 on v4 is a double, low cell then high (ruled 2026-11-14): its raw value printed with D. |
|
||||
@@ -0,0 +1,8 @@
|
||||
make -C v4 post79, run twice on 0a0be0ca's tree (2026-11-20), checking #190.
|
||||
|
||||
- v4/system/post_cases.c and docs/v4.0.0/POST79.md: the same on both runs, and the same as committed.
|
||||
- docs/v4.0.0/POST.md: not the same. POST.md-run1 and POST.md-run2 are the two; run1-vs-run2.diff
|
||||
shows five cells of the "v3 printed" column that differ. Three are addresses (FIND.user_word,
|
||||
>BODY.basic, >BODY.variable), despite setarch -R; two are INFER-VARIANCE@.after_run and
|
||||
INFER-EARLY-EXIT@.after_run, which come of the run's history. POST.md-run2.diff is run 2 against
|
||||
the committed copy. POST.md was then put back as committed.
|
||||
@@ -0,0 +1,18 @@
|
||||
70c70
|
||||
< | `FIND.user_word` | `: test5 44 ; FIND test5 . CR` | stack `empty`, printed `8206544 \n` | unchanged | 0 value(s) left; output not compared | the address FIND leaves is printed |
|
||||
---
|
||||
> | `FIND.user_word` | `: test5 44 ; FIND test5 . CR` | stack `empty`, printed `8206400 \n` | unchanged | 0 value(s) left; output not compared | the address FIND leaves is printed |
|
||||
130,131c130,131
|
||||
< | `>BODY.basic` | `CREATE test9 ' test9 >BODY . CR` | stack `empty`, printed `8207624 \n` | `CREATE test9 FIND test9 >BODY ' test9 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
< | `>BODY.variable` | `VARIABLE var1 ' var1 >BODY . CR` | stack `empty`, printed `8208136 \n` | `VARIABLE var1 FIND var1 >BODY var1 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
---
|
||||
> | `>BODY.basic` | `CREATE test9 ' test9 >BODY . CR` | stack `empty`, printed `8207480 \n` | `CREATE test9 FIND test9 >BODY ' test9 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
> | `>BODY.variable` | `VARIABLE var1 ' var1 >BODY . CR` | stack `empty`, printed `8207992 \n` | `VARIABLE var1 FIND var1 >BODY var1 = . CR` | stack `empty`, prints `-1 \n` | FORTH-83 >BODY takes a compilation address -- FORTH-79's FIND gives one; FORTH-79's ' gives the parameter field already, so v3's ' xxx >BODY goes one too far. v3 prints an address: the case shows >BODY's field is ''s (and VARIABLE's) |
|
||||
144c144
|
||||
< | `INFER-VARIANCE@.after_run` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT . CR` | stack `empty`, printed `0 \n` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT DROP CR` | stack `empty`, prints `\n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') |
|
||||
---
|
||||
> | `INFER-VARIANCE@.after_run` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT . CR` | stack `empty`, printed `23 \n` | `INFER-RUN INFER-VARIANCE@ Q.TO-INT DROP CR` | stack `empty`, prints `\n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') |
|
||||
146c146
|
||||
< | `INFER-EARLY-EXIT@.after_run` | `INFER-RUN INFER-EARLY-EXIT@ . CR` | stack `empty`, printed `1 \n` | `INFER-RUN INFER-EARLY-EXIT@ DUP 0= SWAP 1 = OR . CR` | stack `empty`, prints `-1 \n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') (0 or 1) |
|
||||
---
|
||||
> | `INFER-EARLY-EXIT@.after_run` | `INFER-RUN INFER-EARLY-EXIT@ . CR` | stack `empty`, printed `0 \n` | `INFER-RUN INFER-EARLY-EXIT@ DUP 0= SWAP 1 = OR . CR` | stack `empty`, prints `-1 \n` | the value comes of the run's own history, the same on no two runs or machines: the case as its description has it ('no error') (0 or 1) |
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user