475caf35f4
... and rename it to KEY?. Then, add KEY from KEY? for its blocking version. I need this for an upcoming Remote Shell feature. If a Collapse OS system remotely controls another shell, it needs to be able to poll both the remote system and the local keyboard at the same time. A blocking KEY is incompatible with this. In some places, the polling mechanism doesn't make sense, so this new KEY? always returns a character. In some places, I just haven't implemented the mechanism yet, so I kept the old blocking code and added a "always 1" flag as a temporary shim. I have probably broken something, but in emulators, Collapse OS runs fine. It's an important reminder of what will be lost with the new "dogfooding" approach (see recent mailing list message): without emulators, it's much harder to to sweeping changes like this without breaking stuff. It's fine, I don't expect many more of these core changes to the system. It's nearly feature-complete. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| avra.sh | ||
| common.fs | ||
| forth.c | ||
| forth.fs | ||
| Makefile | ||
| README.md | ||
| stage.bin | ||
| stage.c | ||
| stage.fs | ||
| vm.c | ||
| vm.h | ||
| zasm.sh | ||
C VM
This is a C implementation of Collapse OS' native words. It allows Collapse OS to run natively on any POSIX environment.
Requirements
You need curses to build the forth executable.
Build
Running make will yield forth and stage executables.
Usage
To play around Collapse OS, you'll want to run ./forth. Refer to
doc/intro.txt for help.
The program is a curses interface with a limited, fixed size so that it can
provide a AT-XY interface. If you wish to change the size of that screen, you
need to modify COLS and LINES in both forth.c and forth.fs.
You can get a REPL by launching the program with rlwrap(1) like
this:
rlwrap -e '' -m -S '> ' ./forth /dev/stdin
Problems?
If the forth executable works badly (hangs, spew garbage, etc.),
it's probably because you've broken your bootstrap binary. It's easy to
mistakenly break. To verify if you've done that, look at your git status. If
stage.bin is modified, try resetting it and then run make clean all. Things
should go better afterwards.
A modified blkfs can also break things (although even with a completely broken
blkfs, you should still get to prompt), you might want to run make pack to
ensure that the blkfs file is in sync with the contents of the blk/ folder.
If that doesn't work, there's also the nuclear option of git reset --hard
and git clean -fxd.
If that still doesn't work, it might be because the current commit you're on is broken, but that is rather rare.