It can be a bit hard to find out which bugs were posted about though, considering there are 37 pages

It would be nice if Quigibo would update his first post in the topic with known bugs and if they are fixed or not, yet, so we can figure out which bugs were reported or not for the current Axe version.

Btw, APP compiling works perfectly under OS 2.54 MP (TI-Nspire). I can play APP format games fine, too.

As for bug reports, we ask that people gives enough details (if possible) when posting any. Source code helps a lot, as well as explaining in details. As for grammar, I'm not fond of grammar nazis, especially as someone who don't speak english as native language and forums not being an english class, plus the fact it can be rude towards new members, but we ask people to try doing an effort to at least make sure their posts are understandable. If the reply about grammar was done to a member with like 5 posts, I would have rated down the post, but given it was for a member who have been around for quite a while, I think Quigibo request is justified. I am certain this post I am writing has mistakes, but if a post is very hard to read, it takes considerably longer to understand it, thus, a lot of time lost for the person trying to make sure his APP is clean of bugs.

Cool ^^

On a unrelated note, I was wondering if the error scrolling was ever fixed? I did not get any trouble with it, except when an error was at the very end of the program, it scrolled a bit too far it seems, but I got no side effects of this. What I mean is like:

PRGM:HELLOWLD
:End
:PrintScreenClearEntriesLOLOLOL





Instead of like
PRGM:HELLOWLD
:
:
:A+2->A
:
:
:
:End
:PrintScreenClearEntriesLOLOLOLIn this example, my coding error is the last line, of course. The last time I had this happen was when I tried APP compiling, though (remember the crashes I got on the regular 83+?). I am not sure if it was fixed or not

Ooh ok I see, well I guess you shouldn't worry about this for now. I did not have issues with it so far, it seems, too.

Nice to hear you found it. Also interesting highlighting site you found there

I hope someone can figure out a way around it, though.

Congrats on your 1000th post

It appears that if the last line of a source file is storing a value to a constant pointer, a bad symbol error is thrown if a closing brace is used. The error isn't thrown if the closing brace is omitted.

Some examples that would throw an error:
.AXEPRGM
0→{L₁}.AXEPRGM
[Pic0]→Pic0
A*2→{8*12+Pic0}
Some examples that would not throw an error:
.AXEPRGM
0→{L₁.AXEPRGM
[Pic0]→Pic0
A*2→{8*12+Pic0}
Pause 5000.AXEPRGM
0→{L₁}r.AXEPRGM
Copy(L₃,L₆,{2+L₂}

When i use:

getKey->G
Disp G
I get random binary code


so then I try:

getKey->G
bG->G
Disp G
I get "Err: Unknown Err" on line 2.

This is with an earlier version of the parser. I will update to the latest ASAP and report back if it still persists. I apologize if it has already been handled.

I'm not sure if this has been said before, but it wasn't on the list on page 1. I'm making an app that was originally called AxeMaze, but after a while Axe started compiling it as "Ax." (The period is there for grammatical reasons.) So I switched to BallMaze, and that worked for a while, until Axe started calling it "B." To clarify, the compiled app is being misnamed; the source code is fine.

Also, my app is now giving be a RAM clear when it exits. I don't know why, and I tried changing the code back to how it was, but it didn't seem to help. The problem started when I added DiagnosticOff and Full to the code. I can post the source if necessary.

I'm using a TI-84+ SE and TI-OS 2.43.

When parsing large amounts of hexadecimal data, a few bytes are incorrectly parsed as zeros instead of whatever value the source dictated they should be. This error did not exist in earlier versions of Axe.