Continue my work on EASy68k forth. A few timid steps towards an interpreter. I need more branching words, just hesitate adding more to the assembler portion. I have two inner interpreters, one processes tokens, the other does compiled tokens. Do you look up the word at compile time or at run time? Mostly been working with run time stuff, but I think I like compiled better.
My outer interpreter will probably be incremental, compiling each word as it is entered. This amounts to reading the word, hashing it, looking it up in the dictionary, then storing that address. I may have prefixes for typing numbers (# or $ for decimal, hex). I have a compile flag (will have to compile stuff coming in from the disk) but no immediate words as yet.
EASy68k supports graphics and text, so I will eventually add some primitives for graphics. I just wish there were some way to package the simulator and my code and run it without the debugger interface.
The file interface is very primitive right now. You can save and load from a default file. Sometimes I patch the filename in memory so I can use a second file. I would eventually like to have a block based storage system. Each block in a separate file, loaded and saved on demand.
The hard part with files is covering the error conditions. You must keep track of the status and proceed or not based on that. Perhaps I can start factoring the file primitives. What words should I use here?
Finding more and more each day!