It compiles to about 350 bytes on my calc, so not too bad.  But like i said, if memory is absolutely a problem, you can go with the pixel change option, which is only 170 bytes.

Right, you would replace all the F variables with {L5+1} for example (although i dont think you can use them in for loops ) and then choose a different location for each variable

What are you asking?

no idea, and i dont have any accurate way to time them since axe doesnt have any timer support.  You would try them out and see though.  For the loop method (the second) it takes about a full second to invert the screen though, while the first one does it almost instantly.

^++
Agreed and seconded.

Instant Goto debugging feature FTW.

-A new Axe Parser APP option to get rid of the scrolling when an error is found and you press PRGM to see where is the error located. In other words, an "instant Goto" feature. (like in DoorCS)

I think this would be a great option as well.

Builderboy, that's an awesome routine!

I want to request a feature...
How about jumping to the address in a variable?  Such as Goto {A}, for instance, would jump to A.
And you could have something like [LB]->A to store the address of Lbl LB to A.  This would be useful for jump tables, which is something I really want

Also, user access to the stack would be nice as well.  I would really like to be able to push a variable onto the stack, then pop it off later.

I want to request a feature...
How about jumping to the address in a variable?  Such as Goto {A}, for instance, would jump to A.
And you could have something like [LB]->A to store the address of Lbl LB to A.  This would be useful for jump tables, which is something I really want

Also, user access to the stack would be nice as well.  I would really like to be able to push a variable onto the stack, then pop it off later.

Both of these things are features I am purposely not adding.  The variable goto isn't really used that much in regular assembly and has very limited application.  Its also very easy to screw things up by accidentally jumping to the wrong place and completely messing up the calculator.  I am trying to make it as safe to use as possible, and this is really just an unnecessary danger.  You can do this with a 2 byte assembly code if you really need it.

Pushing and popping into the stack has the same problem.  If you push a variable in a subroutine for instance, then the subroutine cannot return and the program crashes becasue it jumps to the wrong location.  Also, forgetting to pop can lead to stack overflows which are also not good.


The instant goto I'd like to add, but I don't even have the regular goto error working yet so I don't even know how it would be done.  I can do a similar "faking it" sort of thing where it just displays the error instead of going into the editor I guess.