I fourth (fifth?) SirCmpwn's request.  It would really enhance the power of Axe.

Oh yeah, I was planning on adding that functionality.  I'll see if I can get it working.

Oh yeah, I was planning on adding that functionality.  I'll see if I can get it working.

Yay! v1.0.0 is gonna be epic.

But then it's always been epic

Maybe Goto [_LA] might be a better option (or just Goto (_LA)), because braces certainly imply a memory read. That would be kind of like the design mistake Zilog made with jp (hl)

That might confuse people with the way Stop is used, though. And there are always ways to quit immediately from a shell (well, usually).

To quit a program can't we simply Goto a label at the very end of the code?

Well just to be fair, if you do ever find yourself with the need to reset the stack you are probably using bad coding practices or doing something too low level that should be taken care of with an Axiom.  This is for the same reason that "Goto" is so frowned upon in languages like C++.  The main reason I still have it in Axe is because it was really easy to add and should help those used to TI-BASIC, because with all the loops, control structures, and subroutines, you should pretty much never need a goto in your Axe code.

2. Did anyone ever request a Axe( command?;

What would Axe( do? If you mean compiling a source from third-party programs, I suggested being able to do that in ASM Doing that for BASIC would require a parser hook, though.

3. Are there special getkeys for stuff like 2ND+MODE, or do we have to set a variable when 2ND is pressed?.

In ASM, there are several ways to get a key. There's low-level key reading, where you're reading the port directly, _GetCSC, where you're reading each key stroke (this is what Axe uses for getKey, so no 2ND+[MODE] combos), and _GetKey, where you're waiting for a key combo. In other words, _GetKey pauses the program until the next keystroke (no loop required), and if it's a 2ND or ALPHA, it sets the 2ND or ALPHA flag and waits for the next key. Kind of like in the TI-OS, basically.

There could be problems with implementing _GetKey in Axe, though. First of all it has problems of its own. If you do a bcall(_GetKey) in your program and the user presses 2ND+[OFF], the calculator turns off, quitting the program and causing you to lose RAM (since you didn't quit correctly). There are ways to get around that, either with more code or with the undocumented instruction.

If you want to try _GetKey for yourself, here's the hex for it: Asm(EF72496F2600)→K

If you want to try _GetKey without the 2ND+[OFF] thing: Asm(EF0B506F2600)→K