|
|
@@ -636,13 +636,13 @@ Then the two that are *outside* the ladder and gate the goal as stated:
|
|
|
original" (data low, code high) vs a dynamic data base with fixups, and
|
|
|
re-baseline `t43_codewindow` in the same commit. This is the only stage
|
|
|
that blocks *emitting* the whole program.
|
|
|
-14. **Write field widths — THE NEXT RUNG (14330).** `writeln(I:2)`, then
|
|
|
+13. **Write field widths — THE NEXT RUNG (14330).** `writeln(I:2)`, then
|
|
|
`Real:width:decimals`. IoCall parses the expression and then demands `,`
|
|
|
or `)`, so the `:` is ENoSemi. The integer writer needs a width (pad with
|
|
|
spaces on the left); the real writer needs width and decimals. A string's
|
|
|
width also pads/truncates.
|
|
|
|
|
|
-13. **Raise the execution harness's read.** `tests/exec/bootcom.s` reads 16
|
|
|
+14. **Raise the execution harness's read.** `tests/exec/bootcom.s` reads 16
|
|
|
sectors (8192 bytes); `t64_arrays` is already compile-only for that reason,
|
|
|
and CALC's measured `.COM` is **27,901 bytes**. Without this, "executable
|
|
|
tested" cannot be demonstrated for CALC even once it compiles.
|
