I've gotten the file type/extension (whatever you want to call it) implemented. This is only a feature if you're using a compiled token file- otherwise, all files will be given the 8XP file type by default.

I've also added code to automatically archive the resultant files- both for my token compiler (on calc-name is maketok) and Solar89 itself.

I added whitespace support, so Solar89 will automatically discard all extra spaces in front of lines. It won't replace them with : characters or anything like that (that's a way to waste memory)- it just trims them out at the start.

I'm also trying to get empty lines supported, but I'm having some weird issues with that. If the line is at the top of the program, it works fine. If it's in the middle, between two other lines of code, tokenization takes much longer than usual and then it hangs. And if it's at the end, the program runs as normal but the lines at the end don't appear for some reason.

The last problem isn't a huge one (because Solar89 already inserts an extra newline character at the end of the each program), but the first problem definitely is.

I know that, what I meant is if I was using whitespace like this in the text file:

: ClrHome
: Disp "HELLO WORLD"
Then I could either parse it as this:

::ClrHome
::Disp "HELLO WORLD"
Or as this, and save two bytes:

:ClrHome
:Disp "HELLO WORLD"

Oh I see. I would just parse it as the latter. Was it what caused you issues?

Nope, what caused issues would be this:

:ClrHome
:
:Disp "HELLO WORLD"
I've fixed it- partially. Now two empty lines are produced in between instead of one.

I've fixed the bug. And I've released 0.3, with versions uploaded to ticalc.org, Cemetech, and Omnimaga. Can't download until they're approved, though.

The full list of changes are:

-Support for binary token files (with included program- maketok- to make them)
-Support for whitespace in text files
-Bugfix where empty lines in the middle of a program caused infinite loop
-Solar89 and maketok auto-archive output files

Just a few brief updates.

First thing, I made a minor interface change- the tokenizer now outputs each line of the file to the status bar as it runs. I made this mainly to convince the user that the calc hasn't frozen- it's actually doing something. (Since tokenizing can take some time).

Second, I recently wrote another example- a quadratic solver. Just as an example as a slightly longer program (and how much time a mathematical program might be expected to take).

Third, I talked with thepenguin77 earlier today about making a better tokenizing algorithm- a tree based system- to increase speed. I plan to code that when I have the time (unfortunately, not now).

Nice, any screenshot?

Here are two- one of my quadratic solver in the text editor, and one of the Disp "HELLO WORLD" status message (as Solar89 tokenizes a hello world program).

Ah cool. I am confused at the Hello world message, though. I assume it shows the lines of code in the status bar as it compiles? I wonder if it would be too slow for large programs, since Text routines are generally slow?

Right, that's what it's doing.

It's not noticeably slower with that turned on. But if it becomes a problem once the tokenizer itself is made faster, I could make it an option or something.