I don't know if this is because of Axe Parser at all, but seeing as it's only started after I downloaded it, I felt I should post it here.

I've been noticing that certain actions on my calculator have gotten slower and slower. Before, I could archive and unarchive variables under 1 KB almost instantaneously, but recently, it's become really slow. I just tried to archive a mere 68-byte program, and it took four whole seconds. Same goes for exiting Axe: when I first downloaded the app, it exited in less than a second, but now it also takes something like four seconds. Anyone have any idea what's happening? I've already tried RAM clears (dozens of them since I first downloaded Axe -- don't worry, most of them were intentional), and it hasn't helped. I really hope this isn't anything permanent.

You need to garbage collect.  I could have Axe ask you periodically, but I think it would get annoying.

Another bug.
I compiled a 1-KB program with Axe, and suddenly the source (not the executable) became 200 bytes, which means it somehow leaked 800 bytes. I tried to edit the source to check, and it stopped after a statement containing getKey( (yes, it stopped right after the opening parenthesis). I tried to compile it again for no reason, and it gave me an ERR: UNKNOWN ERR. According to your documentation, an ERR: UNKNOWN (that should get updated, by the way ) means that "Something is wrong with the parser. Report bug immediately!" So here it is.

By the way, did anyone figure out what went wrong with my previous bug?

EDIT: Whoops, didn't see your post there, Quigibo. Sorry.

EDIT2: Oh, wow, that was surprisingly simple. It works now, thanks.

EDIT3: I'm talking about the first bug, not the ERR: UNKNOWN ERR.

not sure if this will help, but about deep thought's bug, i had the same thing happen to me when i tried to romdump my calculator about 3 months ago using TiLP. so if you tried to romdump recently it may have been that rather than axe parser.

Axe doesn't seem to cause any problems for me when I did a romdump. I actually did one for my 83+SE today for wabbitemu using rom8x and everything worked perfectly fine. I even left MirageOS, Omnicalc, and CalcUtil installed along with Axe parser, and no problems occurred.

HUGE  (at least for me)

ok this has really been  bugging me.
ok i make a prog, it works.
i am unhappy and get rid of an if statement and the corresponding end command. ( yes the correct one )
i try to compile it again.
it says err. block.
i go and check the code 100 times. *(later on another bug... listed at bottom)*
there is no problem with it..
i finally find out that garbage collect temporary corrects this. ( i think it is only with the newest version of Axe. )


*now other bug*
ok lets go back to earlier
i go and check the code 100 times
i accidentally press enter while at home screen. ( last prog run before failed compile was the successful compiled prog )
screen goes blank
screen comes back on
on the top left corner it displays "program"  (no parenthesis)
them a few seconds later my ram is cleared

I'd like to mention that since AXE is still in developmental stages, it might not be a bad idea to test things out on emulator before running them on a actual calculator. Also, I know this has been said over 9000 times, but backup progress often!!!

Ti-84 plus silver edition
OS: 2.52 MP
Axe: 0.2.6
letter on back: M     (for things like ti-boy se)  ( can't use )

i do have marage os  but i don't compile for it

Is there any reason why you can successfully compile and run Ion programs of large sizes, but when compiling no shell programs that pass about 8200 bytes in (executable) size, trying to run the program returns ERR:INVALID?

EDIT: Also, I guess the whole thing about not running programs larger than 8811 bytes in size (using the Ion-compiled version, as the no shell couldn't run the program, currently at OVER 9000 BYTES!!!!!1!!) may be right though, because I'm currently editing the 4-level grayscale "sprites" of random sections of RAM.

Is there any reason why you can successfully compile and run Ion programs of large sizes, but when compiling no shell programs that pass about 8200 bytes in (executable) size, trying to run the program returns ERR:INVALID?

EDIT: Also, I guess the whole thing about not running programs larger than 8811 bytes in size (using the Ion-compiled version, as the no shell couldn't run the program, currently at OVER 9000 BYTES!!!!!1!!) may be right though, because I'm currently editing the 4-level grayscale "sprites" of random sections of RAM.

Keep in mind that the 8811 limit excludes data, though (example [45892894FCBE8272]->Str1). You could have like 8 KB of code, but then you can still have as much data as you want as long as you have enough RAM to both fit/run the executable.