yes, DJ. basically i'd like an axiom that would read data from L1 and store it to a TI BASIC string var, or Ans. i just want it so i can RCL it later, because i'd be using it for a tilemap editor, and copying a tilemap by hand is a pain in the ass.

And another question: Are we allowed to overload commands (meaning making an Axiom for a command already part of the parser)?

Have you thought about adding double token replacing? something like an Axiom has it's own token and then you just have your next one something like bal(Output( so you can have even more tokens?

I think that would just be confusing especially since it used 2 sets of parenthesis.  The reason I can't have custom names for the Axiom tokens is a lot more complicated than that.  Probably what I will do is have a set of tokens (For instance, the 12 parametric tokens) be named really generic things like Draw1(), Draw2(), Swap(), In(), Out(), New(), Delete() etc. that are specifically reserved for axiom use.

Hmm... although it is technically possible, I was thinking I would just have a different way to add subs form external program data.  But that would be cool to have an option to compile for Axioms.  The only problem is that the current Axioms are too primitive to handle axe calls right now, but that is something I will definitely add later.  I will play around with this idea and see if it's possible.

Being able to use other Axe programs as external libraries would definitely be useful, especially since the only real way to do it right now is to recall the library to the end of every program that needs it.
Compiling to Axioms would be nice too, since you could use tokens to call routines rather than using sub( a lot.

I like both ideas

We have to have Axioms written in Axe. I don't think we want to learn another format. Unless of course you mean having tokens to delimit the routines in an Axe Axiom, which is fine. (As a technical note, Axioms written in Axe will all probably need to be of the kind that are automatically made into subroutines.)
Do you mean precompiled? They have to be compiled in the end. Having them precompiled might not work unless the compiler can generate the equivalent of an ASM list file, which defines labels for external use. A separate compiling mode will probably be necessary for precompilation, but I wouldn't want a whole new compiler.