I know exactly what the problem is with eForth: I’m testing manually by poring over emulator execution traces; I’m not writing tests. I know the inner interpreter and some code words work, so I guess I’ll have to write a test framework out of that, and then test the effects of every other word until I’ve worked it all out. #TDD#FORTH
@jemo07 Hello Jose, I’ve taken an “experimental, untested” port of the late Dr. Ting’s eForth for the Inmos Transputer, and am attempting to finish it, making it work on my portable Transputer emulator. The eForth kernel has ~30 words defined in assembler, and the rest is all in Forth. I’m struggling with the intricacies of the assembler-defined words. They all look OK, but once eForth starts booting, something goes wrong and it emits garbage to the console then causes a memory violation.
@serichards yes it has been ported to many systems, I’m thinking of getting a known-good DOS version (the initial version) installed to verify words I’ve converted to assembler.
Add comment