collapseos/blk/405

: BOOT
    0x02 RAM+ CURRENT* !
    LIT< (parse) (find) DROP (parse*) !
    CURRENT @ 0x2e RAM+ ! ( 2e == BOOT C< PTR)
    0 0x08 RAM+ !  ( 08 == C<* override )
    LIT< (emit) (find) DROP 0x53 RAM+ ! ( 53 == EMITPTR )
    0 0x55 RAM+ !  ( 55 == EMITPTR override )
    ( 0c == C<* )
    LIT< (boot<) (find) DROP 0x0c RAM+ !
    ( boot< always has a char waiting. 06 == C<?* )
    1 0x06 RAM+ !
    LIT< INIT (find)
    IF EXECUTE ELSE DROP INTERPRET THEN
;
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`: BOOT`
			`0x02 RAM+ CURRENT* !`
			`LIT< (parse) (find) DROP (parse*) !`
Add layer of indirection to EMIT This would allow things like temporary giving control to the CL line on the TRS-80. For example... A very far fetched example. Not at all the only raison d'etre* of the layer... 2020-05-01 20:05:15 -04:00			`CURRENT @ 0x2e RAM+ ! ( 2e == BOOT C< PTR)`
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			`0 0x08 RAM+ ! ( 08 == C<* override )`
Add layer of indirection to EMIT This would allow things like temporary giving control to the CL line on the TRS-80. For example... A very far fetched example. Not at all the only raison d'etre* of the layer... 2020-05-01 20:05:15 -04:00			`LIT< (emit) (find) DROP 0x53 RAM+ ! ( 53 == EMITPTR )`
			`0 0x55 RAM+ ! ( 55 == EMITPTR override )`
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			`( 0c == C<* )`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`LIT< (boot<) (find) DROP 0x0c RAM+ !`
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			`( boot< always has a char waiting. 06 == C<?* )`
			`1 0x06 RAM+ !`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`LIT< INIT (find)`
Add layer of indirection to EMIT This would allow things like temporary giving control to the CL line on the TRS-80. For example... A very far fetched example. Not at all the only raison d'etre* of the layer... 2020-05-01 20:05:15 -04:00			`IF EXECUTE ELSE DROP INTERPRET THEN`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`;`