I'm a bit confused about how to read from the Archive.  Let's assume that I want to read data from AppVar MyAppV, which is archived.  How would I do this?  And could I exploit this, possibly with some dummy entries in the VAT, to force a page swap?

By the way, the reason I can't draw the circle or line to the backbuffer is that the routines are hardwired into the primary buffer and are not possible hijack like my other routines.  For instance, the sprite drawing routine defines what buffer it will draw to in the very beginning of the routine so all I have to do is define a different buffer before calling it and then call the routine a little further down than it's normally called, skipping the part about the regular buffer, to hijack it with the new buffer.  This isn't possible with the circle or line since the buffer is defined in the middle.  I would have to write entirely separate routines since they can't share and it would inflate the code.

Ah ha! I found it! I knew you posted something like this a while ago. It sounds like drawing sprites to an arbitrary buffer would be a pretty quick feature to implement 

Yay! I wouldn't worry too much about ClrDraw or DrawInv, as those can be done pretty easily and quickly anyways.

Safty features, I hate how if I make a disp A with no dec at the end, I am screwed with the eternal text displaying

Shaky ground you treadin' on, SirCmpwn. Mind that post's sharpness.

In any case, I would suggest _player's idea of keyhooking the COMPILE command in Axe.

Qazz, it only messes up what's displayed, it doesn't crash. Putting such features could be difficult because Disp A could actually be useful. Not much can be done there
As for using labels literally, yeah, it probably should be reserved as an "advanced use."
The suggestions I've given (definitely "address-of" and less likely advanced operations for "files" (or what I'm calling extended pointers)) probably don't need to be given any "advanced" label, though.
I agree a keyhook to compile would be nice.

I think if advanced commands are added, there should be an advanced section and a warning that those commands are only for experts. Maybe in a different readme file or something. Axe is meant for people who want an easy language like TI-BASIC, so hard commands should probably have a special section. That said, those commands are not a priority at the moment, I think, since Quigibo is focusing on the ease-fullness. I personally find fixed points hard enough so I stayed away from them.

After the new token thing, I learned that it would be best to let Quigibo add features in order he decides to add them or that he wants the majority to add them (poll). I think it is already pretty good, else it would never have been featured on ticalc.org and it would not have 6000 posts. It's not a good idea to badmouth him for not wanting to add a feature, not that it would make the feature get added necessarly, anyway.

Yeah it would be against the rules. There are actually other ways to run ASM, too, apparently, as player mentionned to me once, but that would still be against the rules, too (same for every potential exploits people find)

As for features, you should add 64 level grayscale, pixel shading/ambient light 3D textures and 150 MHz Nspire 84+ emulation mode to the poll.