Oh yeah, you're right, I forgot to check if its archived    Thanks for helping me find that problem!

Looks like your look-ahead parsing still has room for improvement I hadn't recompiled a program using a version newer than 0.2.2 until now, and I've run into a slight annoyance. Your parser threw an error I hadn't seen before, that a static pointer I used was undefined. This is because, to make program editing on my calculator easier, I moved all the sprite data to the bottom of the program and just call it as a subroutine at the start of the program. However, because the program is parsed from top to bottom, it ran into a reference to sprite data in the body of the program "before" the sprite was defined, throwing the error. Any chance this could be fixed? Or an option to disable this part of error checking?

EDIT: So as not to double post, here's another problem I think I may have found, although this may just be inherent in the way text printing works: when large font is enabled, Text() will not display for X=90.

It sounds like you accidentally corrupted your symbol table.  Archive everything you can and reset your ram, that should fix it I think.  The Axe Data file should be really small, I think its like 17 bytes or something.  If it has a ridiculous size, you'll definitely need to delete it.  It doesn't contain any important information, just your compile settings.

Also, guys, if you have a bug in your program when testing and strange things happens, sometimes it's best to archive everything then do a RAM clear before debugging, because then you may continue getting errors or weird stuff happening. You may think it's the program being buggy again, but sometimes it's just the calc being messed up by your previous test.

alright. Err: Undefined
Tribal said this compiled correctly in 2.4... I used 2.5
.SCREEN
DiagnosticOff
[FFFFFFFFFDFDFDFD]->Pic1
ClrDraw
DrawInv
While getkey (doesn't equal symbol here) 15
pause 100
DispGraph
Vertical +
For(A,0,95
Pt-Off(A,0,pic1
end
Pt-On(rand^96,A,Pic1
end


I tried that a lot of times... its error'd on pass2
pass1:  100%
pass2:  69%
err: Undefined

right.. because it doesn't differentiate on the calculator

I think this is a bug. If not just tell me. The following fails to compile:

Code: [Select]

91-sub(CS)
But this successfully compiles:

Code: [Select]

91-(sub(CS))

Not really a bug... more like a lack of feature.  I haven't made subroutines usable in expressions yet although they seem to work anyway for some cases.

@Snake X
I haven't tested that yet, but are you sure you typed it all correctly?  There is nothing wrong with that code.