First, @meishe91, I'm flattered that you cited me as a reference.
Second, a pointer is a value that points to an offset in memory.  For instance, a pointer with a value of 10 points to the 10th byte (actually, it points to the 11th byte because it is zero-indexed, but lets say that it points to the 10th byte for now).  If that place in memory contains code, you can use a pointer to say, "execute this code."  If that place contains data, then you can say, "look at this data."  Code and data look the same in memory, the only difference being that executing data may accidently in your RAM.
Third, here is how applys to Axe, for methods and code:

Code: (Axe Basic) [Select]

ClrHome
sub(SH
Return
Lbl SH
Disp "Hello World!"When Axe compiles, it saves the location of Lbl SH in the first run.  By location, I mean that it saves offset from the beginning.  So, if SH comes 10 bytes from the beginning, it remembers that SH is 10 bytes from the beginning.
The, it hits the "sub(SH" line.  It says to itself, "hey, I know where that is!  It's 10 bytes from the beginning!"  So, it tells the output program to jump to 10 bytes from the beginning, and come back when it's finished.

With storing data, it works the same way.  If you have:

Code: (Axe Basic) [Select]

[0102030405060708->Pic1
Pt-On(0,0,Pic1Axe remembers that Pic1 points somewhere, and then supplys that location to the Pt-On command.

Questions?

On that, no. I think I can do that. My difficulty arises when I want to say... take Pic1 (above) and place it in an AppVar for use by the program in subsequent run. What I'm essentially inquiring about is the conversion from appvar to pointer and back again, without screwing up the data.

And, do all values for pointers have to be in hex?

It helps a little thanks, but it still leaves the part of knowing how to use Axe's commands. I will definately use an array for the reference.

It doesn't necessarily need to be Quigibo who has to do it. There are a lot of people here who could explain it in great detail. Personally, I would do it if I knew more about them (and Axe in general).

Well, it seemed, Quigbo would be best, as he programmed the commands and knows their intricate workings.

Sorry. I keep doing that.

1. No, I didnt have backups, but now im doing it on my computer and using Wabbitemu to test.

Ok. Now, I see the commands for writing to and from pointers, but I'm not exactly sure how to use them or how to get the right bytes. In the TI-Basic version, I had a list containing the following terms:
LP1:

(1): Tackles remaining (max value-200)   
(2): Attack 2 remaining (max value-200)
(3): Attack 3 remaining (max value-200)
(4): Attack 4 remaining (max value-200)
(5): Current HP (max value-70)             
(6): Max HP (max value-70)
(7): Current Level (max value-20)
(: Current Experience Points (max value-1000) ****
(9): Potions Owned (max value-50)
(10): Money Owned (max value-1000) *****
(11): Pokemon Owned (max value-3)

Please can someone tell me how to move this data between the appvar POKE and memory location named anything, preferably a list. I will definiately screw this part up.

And, in your later version, to give a custom name, I open with

.ZPOKEMON
program here

And get Err. Bad Symbol

After you select the name of the appvar, immediately unarchive it.  Then, when you try to do getCalc() you're sure that if it existed, its definitely in RAM and so it only returns 0 if it doesn't exist.

To write data, you have to store the pointer that is returned by getCalc() either in a variable or in RAM.  Then you read and write to that location as if it were any other RAM location.  The same way you would do 100->{L1+6}  You can do 100->{A+6} if you stored the appvar pointer to A.

Thank you. So much. I was having a migraine. But, if I run unarchive on an Appvar, it wont throw an error if it doesnt exist?

This worked...

Output(0,0,"Pokemon
With no closing Quote (Err: Bad Symbol) or Closing Parenthasis (the parenthasis is displayed)


Can an Axe Parser program archive itself?