Just low-key updates to the #Genesis64 parser today.
PRINT now writes directly to RAM and deals with the nasties like TAB(), SPC, and "," and ";".
It also prints out numbers like the #C64 does (leading space for positive numbers, limit display to 10 characters).
Today in "Tales from the code front": adding PRINT to #Genesis64
Actually, adding PRINT wasn't that hard, getting it tokenized *correctly*, was.
You can do nasty things in #C64 #BASIC, like putting spaces between numbers, or skipping the space between functions.
Anyway, it's in now, except for correct handling of "," and ";", as both mess up output/new line handling [as do SPC( and TAB( ]
A new set of #C64 #BASIC v2 functions made it into #Genesis64 today.
I added string-functions (aka.LEFT$, MID$, RIGHT$, as well as STR$ and CHR$), but I still have TAB( and SPC( ahead.
The next thing will probably be adding PRINT in all its glory and with all the naughty oddities.
I don't want to call this coding frenzy, but #Genesis64 now has all 19 #C64 #BASIC v2 numerical functions implemented.
Huzzah!
I spare you the screenshot.
Having some more fun with parsing #c64 #basic in #Genesis64.
I fixed an execution order problem as well as using "-" to negate values.
Numerical functions are in as well, although right now, only SIN and ABS return values (and numbers are not cropped to C64 length yet).
Next stop will probably IF/THEN.
Thank fuck it's Monday.
I did some work on the #Genesis64 parser, the first #C64 #BASIC command is "finally" working (again): LET, as in a=2 (or if you fancy: LET a=2).
And I also did another table (and some pages) from the Commodore Programmer's Reference Guide: "6526 Timing Characteristics".
Bugger me, but tables eat a freaking amount of time to (re)do.
Back to the salt mine now to do some "real" work.
In a rush of motivation, I got back at coding #Genesis64, a #C64 #BASIC parser.
It might help that it's sunny outside (always a plus), and that I had a good idea for dealing with programs and code that should be run directly.
There's also a clean(er) solution for the #parser
So far, I managed to write more (working) code than during the last 4 (dark) months.
Huzzah!
I'm working on #Genesis64 !
I finally had an idea on how to structure this mess and so far it seems to "work".
Let's make this thing parse vars and #BASIC v2 commands ...
Code for fun (#Genesis64), do some #3d (for fun as well), or get out TheC64 and play some #c64 games?
Oh.These.Decissions.
It's been a while since I last worked on #Genesis64. But as everything has been moved to the new server (and I sport a bit of a post-project-depression), I need a few days playing with my own fun project.
Alas, half a day went by, and I'm still digging through my own code, boy, do I need a map.
nGFX