Right, if you wanted to store 10 to A, you could do

10->A

Or you could do

'0A->A

Because in Axe, the ' token means that you are in Hex, and 0A in Hex = 10 in Dec .  Currently the only way to store data into Ram is by Hex, like this:

[010AFF]->Str1

which ends up looking like this in Ram

{1,10,255}

Hopefully in the future you will be able to input data like this as well But no matter how you put the data in, it is always extracted as Decimal.

Well since Axe compiles to Assembly, it means you have control over the entire calc, including allll the Ram All the ram is is really just a long list of numbers.  Each number ranges from 0 to 255 and there are thousands of these numbers in your Ram.  Think of it like a list in Basic, except its a very very large List Well in order to access this list, all you need to do is do

{N}

And you will be able to store to or access the Nth byte in Ram, yay! 

BUT WAIT!!!

Th calculator needs a lot of this Ram for itself, so that it can continue to run, so that there is someplace safe to store all your programs, and so that there is somewhere safe to store the current program.  So you can't just go storing numbers to {0} you'll probably crash your calc .  Luckily Axe provides us with some safe locations that are known to be safe to use.  These locations are stored in L1-L6.  So if you say 5->{L1}, you are actually storing to location 34594, but you would never know that it was safe to store there without being an asm guru So Axe provides you with these locations in the big List of Ram elements that it is safe to store to, and thats there you can keep all your bytes ^^

Except L3 through L6 are not as safe as L1 and L2. You need to read the doc carefully before using them, in case

Well actually A is a number in RAM just like all the other variables.  (Well its a combination of 2 numbers in RAM since its 16 bit, not 8 bit) And indeed you can store numbers to A or any of the other variables if you want But for circumstances where you need a variable amount of number (like an undefined amount of bullets on the screen) you would need a lot more numbers than just A-Z, and an easier way to access them.

Hah, well then we're on the right track because it could be used as both

If you were already using 26 variables and needed more, we could easily substitute {L1} as a variable, and {L1+1} as another ect...

BUT

If you wanted a list, you could do {L1+N} where N is the element of your List (starting at 0) to access a lot of different numbers in the range from L1 to about L1+700.

Not yet (officially) but there is something that does write back on all stored Hex data so that it stays the same between excecutions.  Its in another thread somewhere...

Oh ok, that makes sense