collapseos/blk/398

( This is only the "early parser" in earlier stages. No need
  for an abort message )
: (parse) (parsed) NOT IF ABORT THEN ;

: C<? 0x06 RAM+ @ DUP 2 > IF EXECUTE THEN ( 06 == C<?* ) ;
: C<
    0x08 RAM+ @  ( 08 == C<* override )
    DUP NOT IF DROP 0x0c RAM+ @ THEN  ( 0c == C<* )
    EXECUTE
;

: , HERE @ ! HERE @ 2+ HERE ! ;

: C, HERE @ C! HERE @ 1+ HERE ! ;
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00			`( This is only the "early parser" in earlier stages. No need`
			`for an abort message )`
			`: (parse) (parsed) NOT IF ABORT THEN ;`

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-25 02:10:07 +10:00			`: C<? 0x06 RAM+ @ DUP 2 > IF EXECUTE THEN ( 06 == C<?* ) ;`
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-25 04:10:40 +10:00			`: C<`
			`0x08 RAM+ @ ( 08 == C<* override )`
			`DUP NOT IF DROP 0x0c RAM+ @ THEN ( 0c == C<* )`
			`EXECUTE`
			`;`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00
			`: , HERE @ ! HERE @ 2+ HERE ! ;`

			`: C, HERE @ C! HERE @ 1+ HERE ! ;`