That's a nice idea Builderboy, but unfortunately users have to choose to optimize their own code in cases like this. This is because, although If A=B and !If A-B would form identical control structures, they would not return the same values. And the programmer may want to use the value returned. For instance, the following code would no longer work as the programmer planned if this auto-optimization existed:

If A=5
  →B
  .Do stuff
Else
  .Do stuff
End


Runner, the one I made is much smaller than the one from WikiTI:

p_DispHex:
ld b,4
__DispHexLoop:
xor a
add hl,hl
rla
add hl,hl
rla
add hl,hl
rla
add hl,hl
rla
add a,$90
daa
adc a,$40
daa
B_CALL(_PutC)
djnz __DispHexLoop
ret
It would be about 8 bytes larger to save it to a buffer.  The syntax wouldn't really work well though because axe would throw a fit if you tried to do Disp A►Hex->B for instance since the display routine looks for commas.  You would have to do some hackish code by putting the store on the line after it or using the address of the buffer directly.  But I guess if this is a conversion command rather than a display command this could be allowed... and then I would only need one routine for both display and text.  That might actually work.   I will have to see if I can make that more consistent with the other display format commands because that does sound convenient.

Builderboy.  I really want to but I'm afraid it will break too much compatibility with current Axe programs.  For instance:

:A+1->A
:If A=10
:->A
:End

This code increments A and if it goes above 10 rests it back to 1.  Here you are using the fact that the result of the if expression is a one if it ends up going inside the block.  It would be impossible for me to tell if the next expression is going to use the result of the if expression or not.

NINJA'D!

Thanks Runer!  Its actually kind of freaky how nearly identical it was to my modifications   But I didn't catch that one with the daa since I'm still not entirely sure how that instruction works.

I should be on schedule for an update tomorrow night. 

Actually, I just thought how awesome it would be if Axe supported usb. Even if it was an axiom or something. But, it's such a pain, that I wouldn't ask for it, but would rather do it.

I had an idea:

Disp "Hello"
. THIS IS A COMMENT
Disp "This is not a com."
. THIS IS A NEW COMMENT

What if we could have

...
This is a comment
This is also a comment
This is the third line of the comment
And this is the last line of a multi-line comment
...
Disp "This is not a com."

Multi-Line comments would be very useful for me, and I hope other people too, because I sometimes want to keep 10 lines of code in a program, but hide it for debugging. I have to put a '.' before all lines and that's very tiring on-calc.

Probably someone already suggested this feature, but this thread is 114 pages long :S

Instead of ..., why not have it have an opening and closing comment character. That way, you don't get confused too.

Instead of ..., why not have it have an opening and closing comment character. That way, you don't get confused too.

Yes, '...' was just an idea.

What about

'./


/.'