SamCoVT

#257 is pretty much exactly this and no more. Making portions of Tali optional or using the memory-map features of 64tass have not been started.

I think this can be closed. I've been working with your master-64tass branch for a while now and everything seems pretty stable there. The test suite has been awesome in...

Let leave things as they are for right now and look to re-arrange things with a "v1.1" release where the tass version will become "master". I'll be working off your...

College will be starting up at the end of the month and I have a freshman class this semester, so I'm going to have a lot less free time until...

Thanks for the suggestion, @TheTrueForce . We are indeed evaluating CC65 as one of the contenders for moving to - I agree that having a linker will make it much...

That sounds like a reasonable idea. Does it make sense to leave the forth/user-words.fs file (for stuff users might want on all platforms) and add a platform/myplatform-user-words.fs file for the...

I think that a **round-robin cooperative** setup makes the most sense for Tali as there is no standardized clock. The simulator doesn't have one (although it's easy to extend so...

Regardless of the task type, each tasks is going to need its own return stack if they want to be able to `PAUSE` in something like a `DO/LOOP`. It's really...

I'm just going to put some notes here for when I get to this after the 1.0 release: Merge string.fs and stringlong.fs tests into a single file. They are both...

Hi @svhum, I've taken over maintenance of TaliForth2 (just a few days ago) and I've copied your issue over to: ["https://github.com/SamCoVT/TaliForth2/issues/5"](https://github.com/SamCoVT/TaliForth2/issues/5) Also, you'll likely want to change your upstream over...