I'd rather see a better-optimized BASIC interpreter, but with extra commands (basically the ones available in xLib, with the ability to add more) and and extra options for certain commands. This way people wouldn't have to learn a whole new language that is so different from the majority of high-level languages, and would still be able to run old BASIC games, just at greater speed.
"You're very clever, young man, but it's turtles all the way down!"
Again, I believe any and all languages can be supported. Plugins, my friends, plugins.
Imagine TIGCC for z80. Now imagine TIGCjava. Heck, TIGCfortran even
I think that is getting a bit carried away. Backwards compatibility with existing calc software would be futile. It would require the 'plugin' to recreate an environment akin to what the respected program is used to ... mem adresses, romcalls, all of it.
"My world is Black & White. But if I blink fast enough, I see it in Grayscale."
I think the whole thing is getting a bit carried away . But I'm not going to bring that up in this thread.
That being said, the first and most important thing you guys should think of is how a VAT is going to work, are you going to have extensions or just pre-built in types of files?
necro wrote:I have realised this after a little reading, I had been under the false assumption parts of the OS were hard written and I did not know that everything could be wiped out.
There's always BIOS, you don't want to delete that. BIOS is what you get if you do the battery+DEL thing. (SEND CALC SOFTWARE NOW)
I can't contribute much, but I do have a few routines that might be useful, namely (hopefully) TI-OS compatible link routines. My OS was quite the opposite to yours; all the programs had to be hard-coded, and I got a bit bored after CLS, MODE and SCANCODE... I posted some of the routines in the API thread... *hunts*
Aha, here.