collapseos/blk/082

CURRENT points to the last dict entry.

HERE points to current write offset.

IP is the Interpreter Pointer

PARSEPTR holds routine address called on (parse)

C<* holds routine address called on C<. If the C<* override
at 0x08 is nonzero, this routine is called instead.

IN> is the current position in IN(, which is the input buffer.

IN(* is a pointer to the input buffer, allocated at runtime.

                                                        (cont.)
Move notes.txt in blk 2020-04-14 14:25:14 -04:00			`CURRENT points to the last dict entry.`

			`HERE points to current write offset.`

			`IP is the Interpreter Pointer`

			`PARSEPTR holds routine address called on (parse)`

Stop LOADing on ABORT This is done by adding a "C<* override" layer that is reset to 0 on ABORT. The problem was that when ABORT happened during a LOAD, we had a resetted RSP and started from a clean INTERPRET, but LOAD didn't have the opportunity to restore C<, which caused it to continue interpreting from the faulty BLK. With a C< override, we don't need to restore C<*, we just need to clear the override. 2020-04-24 14:10:40 -04:00			`C<* holds routine address called on C<. If the C<* override`
			`at 0x08 is nonzero, this routine is called instead.`
Replace the "> " prompt with the more traditional "ok" one This is more than cosmetic, it's also highly usable. The presence or absence of the "ok" message allows us to know whether the command aborted. Previously, the "> " prompt appeared when the system expected a prompt in the INTERPRET context, whether the previous command aborted or not. Also, this allows us to get rid of that ugly FLAGS global variable. 2020-04-24 12:10:07 -04:00
Make rdln use system RAM 2020-05-14 14:26:56 -04:00			`IN> is the current position in IN(, which is the input buffer.`
Replace the "> " prompt with the more traditional "ok" one This is more than cosmetic, it's also highly usable. The presence or absence of the "ok" message allows us to know whether the command aborted. Previously, the "> " prompt appeared when the system expected a prompt in the INTERPRET context, whether the previous command aborted or not. Also, this allows us to get rid of that ugly FLAGS global variable. 2020-04-24 12:10:07 -04:00
Make rdln use system RAM 2020-05-14 14:26:56 -04:00			`IN(* is a pointer to the input buffer, allocated at runtime.`
Replace INITIAL_SP with PS_ADDR conf Now I struggle to remember why I ever did things they way I did. There must have been a reason... 2020-05-11 21:08:24 -04:00
Move notes.txt in blk 2020-04-14 14:25:14 -04:00			`(cont.)`