retroclouds, on Thu Aug 18, 2011 7:53 AM, said:
Willsy, on Thu Aug 18, 2011 6:32 AM, said:
GroovyBee, on Thu Aug 18, 2011 5:00 AM, said:
Wow! I like that one! I managed to implement it with a little extra functionality and fit it into the spare space in bank 1 with 2 bytes to spare!
Thanks
So will you consider a 32K (4x8) ROM for the future version of Turboforth? Here's an idea, perhaps add the possibility for loading screens from ROM.
You could use the remaing space to include a standard library of words with super-duper fast access. I don't think the 64K EEPROMS are that much more expensive than 16K EEPROMS nowadays.
The current TurboForth lineage will end with V1.1 I think. I've taken it as far as I can in 16k.
TurboForth 2.0 will probably be 32 or possibly 64K. If I ever start it. Some of the features:
* Compile Forth code to native machine code (not threaded code) with inlining of certain words (e.g DROP DUP SWAP etc would be inlined).
* Multi-tasking
* Bitmap mode
* A full suite of DOS words built in (DIR, COPY, TYPE, FORMAT etc)
* Save/load memory image files
It will essentially be a self contained alternative operating system on a cartridge.
Marc Hull's idea of a multi-banked cart with RAM on it is the target (for me). Multi-tasking requires each task to have its own set of private variables, which can eat RAM, so the idea of 4K of ram in the cartridge is attractive.
Since Marcs cart contains Flash memory, you could also load/save/edit code to 'virtual blocks' contained in the Flash memory chip. You would have access to around 200 blocks actually on the chip, living inside the cartridge. If these were compiled and BSAVED then they would load instantly. :-)
We'll see.