I doubt Axe can screw up programs like this. If it did, it's because you messed with the pointer stuff or used inline assembly. As mentionned in the documentation at the bottom, some pointers can cause instability on the calc. I assume bytes stuff can also pose problems if not used properly too.

In any case, always backup your stuff before testing anything, though. You must never take any chance, especially considering xLIB and Axe are not finished and that there can be errors on both sides (xlib/axe or your code)

Well...ummm...where is A
that's pretty dangerious actually, because whatever te value in A is, that's where you are playing around with. I would recommend using L1/2/3 or maybe defining the bytes in the program with Str1/2/3 etc.
If you define them in the program then it is only as big as you made it. Otherwise if you use L1/2/3 then you would have to look in the documentation to see.

How do you know he didn't do this first:
:L1->A

I use that trick all the time when I have a lot of math like:
:Y*8+X+L1->A

Because that way it can become:
:{A}->B
:15->{A}

Which saves memory and speed if you call it a lot.

I directly assigned that value to {A+1}.
So, that was bad...?

EDIT: Anyone else wake up and immediately log on to Omnimaga, eagerly anticipating the new Axe release every Sunday?

OH! Also, one thing:

When Axe will support Mirage and Ion (and DCS since MOS/Ion progs shows in it), it will be important to be careful to not use RAM areas in your games that are used in MirageOs. I remember Zelda: Dark Link Quest used an ASM utility that did and when exiting Mirage (back when it was in beta, the game showed in Mirage) it crashed. I heard xLIB sometimes had issues, too, with this.

OH! Also, one thing:

When Axe will support Mirage and Ion (and DCS since MOS/Ion progs shows in it), it will be important to be careful to not use RAM areas in your games that are used in MirageOs. I remember Zelda: Dark Link Quest used an ASM utility that did and when exiting Mirage (back when it was in beta, the game showed in Mirage) it crashed. I heard xLIB sometimes had issues, too, with this.

Yeah, it's too bad that Mirage relies on so much. 
You could make your program show up in mirage by putting this on the first line:
Asm(BB6DC930)
However, it may crash, so I'm not trying it.

Yes, it is.  The Hex code I gave earlier is for ion programs, and those don't even have a picture with them.
I think that's the smallest size you could have for a Mirage program.  It's only 4 bytes bigger than a non-ion program after it's compiled. (I think)