Wow!  The results are already out?!? 

That is so cool!  I can't believe it was by such a big margin too, I really thought it was going to be close. Thanks everyone for all the support, I couldn't have done it without you guys.  From the beginning I never thought it would take off like this and actually be this popular and especially this early in development since a stable version still isn't out yet.  Also, I've noticed that more than half of the new 83/84 assembly programs being released currently are written in Axe and its not just forum members here either.  So I think the project has been quite successful overall 

Also, its great how each of the top 4 nominees ALL had their own programming language or language extension!

Oh you're right.  But I just realized that your other optimization doesn't work either. You cannot do this for AND:
!If A-EXP1 + (B-EXP2)This doesn't work because there are more solutions than there should be.  For instance, if A were EXP2 and B were EXP1 the expression would be zero when it should be non-zero.

But you can do this for a compound OR:
If A=EXP1 + (B=EXP2)
And you can do this for a compound AND:
!If A-EXP1 [16-bit or] (B-EXP2)
And speaking of optimizations.  One major optimization that usually gets ignored is recycling large axe commands.  Axe is not like BASIC and so each command needs its own subroutine to add to your program.  For instance, lets say you use Pt-On() and Pt-Mask() in your code.  Each one has to bring its own 100+ byte subroutine into your program.  But you can probably get away with having just a Pt-Mask routine, recycling it to act like Pt-On by simply adding a 2nd layer to your sprite which is only 8 bytes extra instead of 100ish.  Or you could do the opposite too and only have Pt-On() and Pt-Change() to manually change both buffers at once.  This generally reduces the overall size of the program by a lot when you use the routines only once or very rarely in your code.  And I don't mean calling it rarely, it could be the most used routine in your code, I just mean rarely appears in your source.

More examples: You can draw pixels and boxes with just sprite commands.  Boxes can be drawn with just pixels or lines.  Strait lines can be drawn with just boxes or pixels.  Its best if you only have one type of DispGraph in your all your code.  Pre-flip sprites so you don't need the flip commands in your code.  etc.

The only downside is that it slightly reduces the speed since its not as specialized but its usually worth it because you save a lot of memory, especially in smaller programs.

By the way, you can't have non-constant data as part of the Data() command.  And that whole inData() optimization only works for comparisons with numbers between 0-255.  You can optimize it to this always though:

!If A-EXP1 [16bit and] (A-EXP2)

Back from my trip!

Multi-line comments is a good idea, I must have forgotten about it.  I like the original idea of "..." as the start and end since that reminds me of how python does it and you don't have to go into any menus to get the tokens so its easier to type.

Break and Continue are still maybes mostly because I would have to create new tokens for them and they wouldn't be in convenient places next to the other program flow commands.  I'm mostly going to be working on the Axiom support for the next few days since I feel that's most important (After that, anyone can add whatever command you want to the language)

Yup, so the last of the betas is out (hopefully).  Now is the time to catch those bugs so 1.0.0 can be as bug free as possible.  I would also like to get a small group to test pre-releases so that I can be more confident in the stability.   The only requirement is that you have at least one very large file and a variety of programs to test it on.  I am also interested in an assembly programmer who wants to get a head start writing an Axiom so I can have another example to play with in addition to my mode 7 Axiom.  Examples of possible Axiom projects: CalcNet, Raycaster, DCS GUI interface, Fast Math Library, or anything else you can think of.

I'll be gone for a few days, but I'll start picking volunteers when I get back.  There will probably be a bias to more experienced Axe programmers since I only need a few.

:For(A,0,20)
:A*B->C
:End

Can be changed to:
:-B->A
:For(D,0,20)
:A+B->A->C
:End
And now you've removed a multiplication.  If you add rotation, you have to do 2 additions: one for the Y spacing and one for the X spacing.

Speaking of bugs I FINALLY fixed the input command.  It took quite a bit of disassembly since its not documented anywhere.  Turned out the buffer that needed to be cleared was "ioPrompt" at $8D5F.  There is even a bcall to do that.