Page 3 of 3

Re: 6502 TaliForth2 Implementation Questions

Posted: Thu Mar 06, 2025 12:06 am
by SparkyNZ
Finally! Just hacked the backslash glyph too.. If only I had more time right now to look at that editor! :-)
TaliWorks3.png

Re: 6502 TaliForth2 Implementation Questions

Posted: Thu Mar 06, 2025 5:12 pm
by SamCoVT
That looks great.

The double "compiled" is likely because your text file has both carriage returns and linefeeds at the end of lines. Tali accepts either as an end of line marker. Reading from files, especially if saved in Windows/DOS format, may have both characters at the end of each line. If that is the cause, the solution might be just filtering one of them out (whichever one the ENTER key doesn't give you, so that ENTER still works properly interactively).

Tali's built-in load and save features use blocks and require the user to write the routine(s) to load and save a 1K chunk of data to/from RAM to permanent storage. There is a RAM drive built in to let you play with the words if you don't have the permanent storage worked out yet. If you run through the tutorial on using blocks, you should get enough of a feel for what's going on.

You certainly should be able to strap your screen editing on the front and just copy the data from the block buffer in RAM to/from the screen. You can use the RAM drive to get started with that and implement the PC file backend later. Traditionally, Forth screens are arranged as 16 lines of 64 characters with spaces in all unused locations, but you really can arrange them any way you want. They just need to represent a continuous 1K chunk of memory, and Tali runs them (using the LOAD or THRU words) by loading the entire 1K chunk and evaluating it as a single string.

Congrats on getting things working!