Yes I did.  You have to add >Dec when displaying numbers in base 10.  Otherwise, it things you are displaying the string at the location of B.  I really couldn't think of any other way to have the same command be able to display in 2 different formats since it doesn't know which one you're talking about.

Edit: ninjad'

Just fyi, 1.5x slower was an upper estimate.  Most games will spend the vast majority of their CPU time drawing sprites and copying the buffer to the screen, which is same speed as pure ASM anyway, so there will be no considerable difference with regular asm speed.  The slowdown would only be noticeable if you had to do intense computations like trying to do 3d graphics or large particle effects or something like that.  In the case where you do need some "really fast processing" you can always write it in assembly and include it in the program.  You could for instance import an entire ray casting engine into the program but write the actual game mechanics in axe parser and it would probably be a lot easier to program than if the entire thing were assembly and run at about the same speed.

@ProphetsDementia
If you want to see how it works, download the latest version.  It comes with 4 example programs so you can get an idea about how the syntax looks.  I also included a complete instruction set.

I am trying very hard to make sure that every new version only adds features and is reverse compatible with older versions.  Occasionally I may have to make some changes, but they will always be minor and easy to fix.

You can still leak in Axe Parser, but only by calling a subroutine that keeps calling itself in a non-terminating infinite loop.  I mean, you can have subroutines call themselves if you want to have a recursive subroutine, but it has to actually exit somewhere.  All the other commands are leak-proof unlike basic.

The next update will definitely have Else, but I'm not sure if it will have the Ternary operator since I have so many other things to do.

Btw, the buffer is stored in plotSScreen.  What would be the use of copying the screen to the buffer?  All of the drawing commands draw to the buffer anyway.

Yeah, the sprites right now are not clipped.  I was thinking of adding that, but I was kind of in a hurry.  That would be great if you can optimize a routine for me!  I need it optimized for size, not speed though.

I'll get working on Else soon.  You can do this in the mean time:

If <statement>
<code to do if true>
Goto 1
End
<code to do if false>
Lbl 1
Delvar 1

The asm code generated from this will be identical to the code generated when using Else.

New update is here!  Expect a new update every Sunday from now on I think.

This version is much more powerful, but still lacks data structure manipulation for complex games (you know, lists and matrices and stuff).  But that will be what I'm going to work on next.

I also included a tiny optimization tutorial with some stats.

False.  In BASIC, its actually 2 bytes since you have to include the [Enter] character or the colon to get to the next instruction (I think only DelVar doesn't require this).  This type of next line character isn't needed in assembly, so its only a 1 byte difference.

Check this out:

http://en.wikipedia.org/wiki/Bresenham%27s_line_algorithm

Its probably what I'll be using, it only requires addition and bit-shifting, no floats.