collapseos/emul/run.fs

: EFS@
    256 /MOD 3 PC! 3 PC!
    1024 0 DO
        4 PC@
        BLK( I + C!
    LOOP
;
: EFS!
    256 /MOD 3 PC! 3 PC!
    1024 0 DO
        BLK( I + C@ 4 PC!
    LOOP
;

: INIT
    CURRENT @ HERE !
    BLK$
    ['] EFS@ BLK@* !
    ['] EFS! BLK!* !
    RDLN$
    LIT< _sys [entry]
    ." Collapse OS" CRLF
    INTERPRET
;
blk: first steps 2020-04-14 23:05:43 +10:00			`: EFS@`
			`256 /MOD 3 PC! 3 PC!`
			`1024 0 DO`
Add word "BLK!" as well as emulator support for it. We can now write an edited block back to "blkfs". 2020-04-17 07:22:18 +10:00			`4 PC@`
blk: first steps 2020-04-14 23:05:43 +10:00			`BLK( I + C!`
			`LOOP`
			`;`
Add word "BLK!" as well as emulator support for it. We can now write an edited block back to "blkfs". 2020-04-17 07:22:18 +10:00			`: EFS!`
			`256 /MOD 3 PC! 3 PC!`
			`1024 0 DO`
			`BLK( I + C@ 4 PC!`
			`LOOP`
			`;`

blk: first steps 2020-04-14 23:05:43 +10:00			`: INIT`
			`CURRENT @ HERE !`
			`BLK$`
			`['] EFS@ BLK@* !`
Add word "BLK!" as well as emulator support for it. We can now write an edited block back to "blkfs". 2020-04-17 07:22:18 +10:00			`['] EFS! BLK!* !`
blk: first steps 2020-04-14 23:05:43 +10:00			`RDLN$`
Add word "EMPTY" 2020-04-15 06:07:07 +10:00			`LIT< _sys [entry]`
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			`." Collapse OS" CRLF`
blk: first steps 2020-04-14 23:05:43 +10:00			`INTERPRET`
			`;`