Perfect character spacing when displaying text one character at a time.
That is the feature I want.

^ I'll get to that character thing  soon.

I'm thinking of allowing a new alternative syntax to make coding a little easier.  Just like you can do {L1+5} I am thinking of also allowing L1(5) like how BASIC does it.  You would also be allowed to do this with variables.  That is, A(2) becomes {A+2}.  The only downside to this would be that implied multiplication can never be implemented then becasue using parenthesis will ALWAYS imply pointing and never multiplication in order to make this unambiguous.  Not that I was planning to add implied multiplication, but thought I'd mention that.  Similarly, I would also like to be able to do the same with matrices.

What I was thinking is that you can store to a matrix at the beginning at some point.  So L1->[A](5,10) tells the compiler that you would like to start a Matrix at the position L1 and make it 5x10.  This would be completely a compiler command and would not contribute anything to the code.  The next step would be to use [A].  With the new syntax, you could say something like [A](2,4) and it will compile as {L1+2*5+4} since now the compiler knows where to store the matrix and how big it needs to be.

I'm still not sure how possible this will be to do since I still need to have it optimized automatically, but it would certainly be pretty cool.  It might allow me to implement some other commands like row and column swapping as well as well as filling with a single value, copying one matrix to another, etc.  All handled at compile time by the parser to translate into the current way of doing things so that its just as efficient.

I'm not planning to ever replace the old syntax, I'm just giving a new alternative to those who like the BASIC way of doing it.

Wow that actualy sounds amazingly epic!  Automatic Matrices and Auto lists and all sorts of other magnificent things I wonder... if matrices could be 'initialized' to half byte in order to take the hassle out of using half byte code :O

^ I second that request.

sorry for being slow...but what will that allow us to do that the current code won't?

It will allow us to change other if's.
:56→V
:If V
:Disp "V is not zero"
:End

Currently that would cause the parser to think, oh, its not a 1, so skip the block

I think it needs real Booleans. 

I also like the matrix/list idea.

I think it would be nice indeed if it worked like TI-BASIC. I always had trouble with If conditions otherwise

It would be nice if there was a way to delete appvars from within your Axe program.