collapseos/blk/393

: RAM+ [ RAMSTART LITN ] + ;
: BIN+ [ BIN( @ LITN ] + ;
: HERE 0x04 RAM+ ;
: CURRENT* 0x51 RAM+ ;
: CURRENT CURRENT* @ ;
: XYPOS 0x40 RAM+ ;

( w -- a f )
: FIND CURRENT @ SWAP _find ;

: QUIT
    (resRS)
    0 0x08 RAM+ !  ( 08 == C<* override )
    LIT< (main) FIND DROP EXECUTE
;
1 25 LOADR+ ( xcomp core low )
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00			`: RAM+ [ RAMSTART LITN ] + ;`
icore: add BIN+ This allows us to write LATEST at proper offset in emul/stage1.fs in cases where we set a nonzero BIN(. 2020-04-30 01:42:09 +10:00			`: BIN+ [ BIN( @ LITN ] + ;`
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 0x04 RAM+ ;`
			`: CURRENT* 0x51 RAM+ ;`
			`: CURRENT CURRENT* @ ;`
sms: CollapseOS prompt! 2020-05-16 02:14:27 +10:00			`: XYPOS 0x40 RAM+ ;`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00
			`( w -- a f )`
Rename (find) to FIND I hadn't noticed that this word was almost ANS compliant. 2020-05-16 02:50:14 +10:00			`: FIND CURRENT @ SWAP _find ;`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00
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			`: QUIT`
			`(resRS)`
			`0 0x08 RAM+ ! ( 08 == C<* override )`
Rename (find) to FIND I hadn't noticed that this word was almost ANS compliant. 2020-05-16 02:50:14 +10:00			`LIT< (main) FIND DROP EXECUTE`
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			`;`
Move core's blk to xcomp core (low and high) TODO: implement X['] so that I can remove those XCURRENT patterns. 2020-05-14 00:14:23 +10:00			`1 25 LOADR+ ( xcomp core low )`