Just a thought:

IIRC, Axe compiles all the code and skips all the data on the first pass. Then, on the second pass, it appends all the data to the end of the compiled program, creating space as it sees fit. What if these commands were made:

FnOn -  Activate BASIC command mode.
FnOff - Deactivate BASIC command mode.

Here's where my idea comes in.
What if Axe made three passes? The first pass would check to see if there are any FnOn or FnOff commands in the program, skipping everything else. The second and third passes would be the normal Axe compilation.

For example:

First Pass:
Check for any FnOn and FnOff commands. If so, save that line and skip over all code until the end of the program is reached or the FnOff command is reached.

Second Pass:
Compile programs.

Third Pass:
Append data.

So, penultimately, the program code is the ASM version of this.

:Asm(prgmAXE1
:<TI-BASIC code>
:Asm(prgmAXE2
 

tl;dr: Axe should compile subroutines and insert them into a large ASM program if BASIC commands are possible.

Of course, all of this is useless if Quigibo figures out a way to reuse commands for different purposes.

I can has latest SPASM compatible ti83plus.inc file?

Oh!
Before I forget, I'm going to throw this out there.

The Chapters I upload here ARE NOT THE FINISHED PRODUCTS!
Think of them as an advance reader's copy.

I still have to grammar check and trim the things.

I believe that you store that data into another variable.
Then, use that variable normally.

[Pic1]->GDB1
EDIT: Also, does anyone know what DATA→NAME does? Use? Practical application?

I understand.

Perhaps when it is finished, I'll translate it into another language.

Chapter 2 up.

I'm getting the feeling that storyline is a key element in this.