3 ms·
This is fun too https://github.com/howerj/subleq/ but you might need to edit subleq.fth and create a new image with some of the constants named opt.*
by anthk 1y ago
This is fun too
https://github.com/howerj/subleq/
but you might need to edit subleq.fth and create a new image
with some of the constants named opt.* settings set to 1 (enabled) in order
to enable do...loop support and such. After you enabled them, try ./sublec ./sublrec.dec < ./sublec.fth > new.dec, wait a lot, and then run ./subleq sublec.dec .
In order to save lots of time, clone the muxleq repo https://github.com/howerj/muxleq https://github.com/howerj/muxleq , edit muxleq.fth as always, and then run ./muxleq ./muxlec.dec < muxlec.fth > new.dec, and ./muxlec ./new.dec to run the new DEC EForth image.
Is not especially fast but it's a ready to run Forth and the Subleq machine can be compiled even under Windows XP and up with Min-C or any bundled C compiled on GNU/Linux BSD, from cproc to tcc, gcc or clang. If some of your code runs fast under Muxleq+EForth, it will fly under PForth and GForth.
https://minc.commandlinerevolution.nl/english/home.html https://minc.commandlinerevolution.nl/english/home.html
The speeds I get under an n270 atom with Muxleq are almost like a Forth machine under a boosted up 8 bit machine, kinda like an 8MHZ z80 with a native Forth, or a very low end M68k machine.
- anthk 1y agoWell I made a typo in the former comment; in order to run the NEW subleq.fth image, as you might guessed it's './subleq ./new.dec' . I post this because I can't edit my comment any more.