Scot W. Stevenson
Scot W. Stevenson
Requires #250 and #251 to be finished. Rewrite Tali in the new version of assembler in just the way it is, so we can use the existing test scripts with...
Once we are switched to 64tass, we're going to have two versions of Tali, one with the old assembler Ophis, which I would only keep for bug fixes, and one...
@SamCoVT first, thank you again for all the work. Tali wouldn't be even close to where it is now without you. The question is what steps are to come next....
The custom setup for documentation was fun, but Sphinx (developed for Python documentation) solves these problems in a simply, standardized way and can be combined with Read the Docs. For...
Neither ANS Forth nor Gforth come with a standardized wordset for multitasking, let alone a reference implementation of some sort. The consensus on 6502.org seems to be that it can...
The testing folder could be reorganized - Gforth tests should go in their own file (having them run as "Tali" is not polite), there might be some logical way to...
In `question_do_runtime` of **?do** (about line 3211 in `native_words.asm`), there are the two jumps ``` jsr xt_two_dup jsr xt_equal ``` that should be converted to lower-level assembler for speed.
`#` in `native_words.asm` looks like it can be optimized for speed and maybe even size.
Slash is one of those words that we probably want to make as fast as possible. Some parts are still simple subroutine jumps.
It is pretty likely that users will have one or more ZFS datasets ("shares") for Plex/Emby/Jellyfish, so it might be worth provided an example Sanoid configuration for snapshots of these...