collapseos/blk/813

( BOOT DICT: There are only 3 words in the boot dict, but
  these words' offset need to be stable, so they're part of
  the "stable ABI" )
'E' A, 'X' A, 'I' A, 'T' A,
0 A,, ( prev )
4 A,
H@ XCURRENT !        ( set current tip of dict, 0x42 )
    0x17 A,          ( nativeWord )
    HLT,
CODE FOO
L1 BSET
    AH 0x0e MOVri, ( print char ) AL 'X' MOVri, 0x10 INT,
    L2 BSET JMPs, L2 @ RPCs,
;CODE
pcat: begin structuring around words 2020-06-15 04:15:44 +10:00			`( BOOT DICT: There are only 3 words in the boot dict, but`
			`these words' offset need to be stable, so they're part of`
			`the "stable ABI" )`
			`'E' A, 'X' A, 'I' A, 'T' A,`
			`0 A,, ( prev )`
			`4 A,`
			`H@ XCURRENT ! ( set current tip of dict, 0x42 )`
			`0x17 A, ( nativeWord )`
pcat: begin porting forth I'm not sure yet where I'm going, but I'm not going to build the 8086 port from the ground up like I did with the z80, that is, making is sustain itself and eventually merge its forth code with core words. That would be too much work which would then be thrown out (all those words I'll initially have to implement in asm which are already implemented in Forth). What I think I can do is build a mirror version of z80 boot code and cross-compile it from the z80. This means it has to follow z80 stable ABI. Nope, I'm not sure where I'm going... 2020-06-14 11:37:54 +10:00			`HLT,`
pcat: begin structuring around words 2020-06-15 04:15:44 +10:00			`CODE FOO`
			`L1 BSET`
			`AH 0x0e MOVri, ( print char ) AL 'X' MOVri, 0x10 INT,`
			`L2 BSET JMPs, L2 @ RPCs,`
			`;CODE`