This isn't exactly relating to Axe Parser, but I figure this would be a place where people might be able to answer my question: Is there any way to retrieve a compiled program from Wabbitemu? I'd normally use my physical calculator but I can't manage to get the link to work any more.

Yeah, at the moment I'm making as many optimizations by putting mathematical or logical expressions used more than once (as long as it's size efficient to do so) into subroutines, because my program is at about 7.5k and I don't mind sacrificing some speed for space (it's a sprite editor after all, no need for speed)

EXP1·EXP2
EXP1+EXP2
EXP1☐EXP2

Returns respectively the bitwise "and", "or", and "xor" of the two expressions. These are the plot style tokens.

can someone explain to me how these work?

These compare each bit in EXP1 individually against the bit in the same location in EXP2. Some examples follow.

---

255 (00FFh, 0000000011111111b) and 43690 (AAAAh, 1010101010101010b) = 170 (00AAh, 0000000010101010b)

      0000000011111111b
and 1010101010101010b
      0000000010101010b

---

255 (00FFh, 0000000011111111b)  or  43690 (AAAAh, 1010101010101010b) = 43775 (AAFFh, 1010101011111111b)

      0000000011111111b
or   1010101010101010b
      1010101011111111b

---

255 (00FFh, 0000000011111111b)  xor 43690 (AAAAh, 1010101010101010b) = 43605 (AA55h, 1010101001010101b)

      0000000011111111b
xor  1010101010101010b
      1010101001010101b

---

I've actually been working on an Axe sprite editing program myself. As of now, it supports:

• 8x8 and 16x16
• Multiple realtime zoom views
• Realtime hex display
• Hex input
• Flipping horizontally/vertically
• Rotating
• Opening and saving as many sprites as memory allows
• Help screen (with nice scrolling!) Had to scrap this to save 850 bytes, program was getting too large

The real trick will be fitting in features like grayscale with my program already over 7 KB.

The following is a list of all screen/buffer commands, with the size of the routine indicated in parentheses:

• ClrHome (6)
• ClrDraw (3)
• ClrDrawʳ (6)
• DispGraph (46)
• DispGraphʳ (63)
• StoreGDB  (6)
• StorePic  (11)
• RecallPic  (11)
• DrawInv  (17)
• DrawInv ʳ (20)
• Horizontal + (18)
• Horizontal - (18)
• Vertical + (13)
• Vertical - (13)
• Shade() (8)

The following is a list of the screen/buffer commands that do not utilize subroutines and the increase therefore in program size if the command is called 1, 2, 3, or n times compared to if it was called using subroutines:

• ClrHome (-4, -1, 2, 3n-7)
• ClrDraw (-4, -4, -4, -4)
• ClrDrawʳ (-4, -1, 2, 3n-7)
• StoreGDB  (-4, -1, 2, 3n-7)
• StorePic  (-4, 4, 12, 8n-12)
• RecallPic  (-4, 4, 12, 8n-12)
• Shade() (-4, 1, 6, 5n-9)

Perhaps you could add an optimization feature that counts the number of references to commands such as these? This would either include the routine inline or in a subroutine that is called multiple times depending upon which method is more size efficient based on the number of times the routine is called.

I like using TI ProgramEditor for a few reasons. Firstly, the program is always stored on your computer and you don't have to worry about it's safety. Secondly, running it through an emulator that you don't have any important data on and that can't become damaged is always nice. Thirdly, you can view indented code much more easily, which I always do to make the program more understandable. Fourthly, there's no taking a minute to scroll from one part to another in massive programs, which is helpful for projects such as the monstrous sprite editor I'm working on now, the compiled code of which just passed 7,000 bytes. Finally, it's easy to move around code. This often comes in handy when I realize I perform certain actions multiple times in the program and that I could save space by instead making that code into a subroutine and just calling it from those multiple places.

EDIT: In response to DJ's post below me, you know it only takes all of like 3 seconds to drag and drop the file to the emulator.

I'm just going to post this here for people who want to post more accurate-looking code. These are special characters to better represent calculator symbols:

→
L₁
L₂
L₃
L₄
L₅
L₆
θ
∆List
≠
≤
≥
·
﹢
□
√
²
ʳ
▸Frac
▸Dec