Very nice, multiplication too?  And rotation commands?

The full list is included in the zip file in the optimizations file.  I know its easy to miss, so here is a copy of it:

================================================
List of expressions with automatic optimizations
================================================
Expression______Bytes___________
+VAR            5
+CONST          4
+1              1
+2              2
+3              3
+256            1
-VAR            7
-CONST          4
-1              1
-2              2
-3              3
-256            1
*VAR            7 + sub
*CONST          6 + sub
*2              1
*3              4
*4              2
*5              5
*6              5
*7              6
*8              3
*9              6
*10             6
*12             6
*16             4
*32             5
*64             6
*256            3
/VAR            7 + sub
/CONST          6 + sub
/2              4
/128            5
/256            3
^VAR            7 + sub
^CONST          6 + sub
^2              5
^4              6
^8              6
^16             6
^32             6
^64             6
^128            4
^256            2
=VAR            12
=CONST          11
=SHORT          10
=0              8
=1              8
=/=VAR          12
=/=CONST        11
=/=SHORT        10
=/=0            7
=/=1            8

SHORT means less than 256 bytes
CONST means any size
=/= is a "not equal sign"
I'm aware there's more I can add, I'm just focusing on other more important things at the moment.

Yeah it doesn't account for the variable loading.  Its 3 bytes to load variables or constants before you actually do the operation.

Also Axe is much much much faster than BASIC.  Remember that it requires a whole new mindset.  The only time you ever have to worry about speed is with very intensive drawing and computation.  For instance more than 20 sprites with collision detection, event handling, and maybe some AI code.  And even then, the speed increase is usually a very small fraction of the total cycles.  Most cycles go into displaying sprites usually.  That's why I always optimize for size.

And of course I say "usually".  You can always optimize these things yourself even though its not automatic.

Does Axe have rotation and bit logic?

What would be bit logic?

aaaah ok. Wouldn't that be complicated to use, though?

What would be an example (maybe some sort of Axe pseudo code) of it in action and example of what it would do?