check your code,  When i was optimizing, i think it was gravitater, I had used Else!If more than 11 times consecutively.

I've used as many as 20 in a row, it might be another problem with your code.

Same (although apparently it gets really unoptimized). I still can't seem to find a pattern for when there's a bug with ElseIf. I know earlier versions of Axe occasionally messed up on nested If - ElseIf - End loops randomly.

A very odd bug:
I am currently running 2.55MP on a TI84+SE.
The calc has Axe 0.5.0 and DCS 7.1.
I don't have much context to this problem, but I will explain it as well as I can.
I had a source code for my upcoming (and still unannounced) game in the RAM. 
As I compiled it, Axe saved a backup like usual.  When Axe finished backing up, I opened the Prgm menu. 
The numbers to the left of the program were all scrambled up, and some entries were shown multiple times while others were not shown at all.

Next, I opened DCS to see if the bug screwed up the folders and everything else.  Fortunately, it did not. 
Once I saw that everything (the programs itself) should be okay, I restored the backup and recompiled it. 
This time, the compiling screen (not "backing up") froze.  I was forced to remove a battery. 

After the RAM cleared, I was able to restore the backup and compile it again. 
The menu was back to normal, and the compiled program ran fine. 

A similar problem happened. 

This time, Axe did not freeze.  It seemed to compile like usual. 
When I tried to open any Flash Apps, it said "ERR: Validation".  It also messed up the menu screen (see quote above).  Also, one of my subprograms went missing from the archive. 

Oh, sorry. I meant 0.5.0.  I will try to resend the app.

The weird thing is that it only happens sometimes.  When I try to compile the same source again, Axe works fine. 

I am using a TI-84 Plus SE (no extra ram).

Yes, there was free ram and archive.  (Again, the weird thing was solved with a ram clear )

New bug: Apparently Axe adds two after finding a pointer to a real var after using GetCalc(, even though it isn't needed (you probably already know about this).

Ah, didn't see that. Which reminds me:

• Quote from: juju2143 on February 15, 2011, 08:35:53 pm

  I compiled an Axe program so it would output an Application, but I didn't had enough archive. Naturally, it error'd. Then I found out with Calcsys it created an unnamed, 0xC6050500 byte (3 GB?) application in the archive. Now the Arc Free counter in 2nd+MEM is stuck to 0 bytes left.
• Quote from: Builderboy on February 15, 2011, 09:35:50 pm

  So with Axe 5.0 I am getting some random Err:Symbol errors when a program is archived, as well as sometimes reporting a picture is missing, even if it is not.
• Quote from: Builderboy on February 18, 2011, 02:11:24 pm

  A and not(B) throws an symbol error it seems not() cannot be used inter expression?
• Quote from: Runer112 on February 22, 2011, 03:48:22 am

  I don't know if this is more of a bug report or a feature request, but none of the GetCalc() routines account for real and complex number variables lacking a 2-byte header. I would suggest the following changes.
• Quote from: Freyaday on March 05, 2011, 08:31:04 pm

  L3->DispGraph and L6->DispGraph both produced
  Unknown Err
  Code: 4726231
• Quote from: Runer112 on March 11, 2011, 12:54:03 pm

  Quigibo, perhaps implement B_CALL(_DelRes) somehow? It would probably have to be manually called by the user at their discretion, but it would be useful for people who want to use L₂. And for that matter, B_CALL(_DelRes) should probably be a part of the interrupt setup, which it currently is not.
• Quote from: Darl181 on March 20, 2011, 02:46:13 am

  If I use Else!If more than 11 times consecutively, the parser throws ERR:BLOCK
  btw there's some complex Pt-On( 's between them, maybe it could have to do with # of bytes in the block?

A list of all reported bugs since 0.5.0 was released.

[0000000000000000]->Pic0->Pic2
Does not work.

I'm not really sure why you would want to do this. If you have already defined the data as Pic0, defining it again as something else would just be a waste of symbols.