You can only see the word FastCopy so many times before you feel like a retard.

If anyone could put some of the commands in layman's terms...?

FastCopy is just a name of an assembly routine.  It has nothing to do with Axe Parser itself other than that Axe uses this routine (err.. it doesn't anymore, it used to).

The instruction set lists it in the documentation as:

DispGraph - Draws the buffer on the screen.

I think its a pretty straightforward command.  Do you have any questions in particular?  I haven't made an Axe tutorial yet and I don't think I will even get started until its more stable.  The best thing to do is look at the source code for the example programs and play around with it.

EDIT:
L1-L6 are just locations in RAM.  When you write {L1+4} you are saying "The byte that is 4 bytes after the location of L1" just like you would do L1(5) in basic.  It would be 5 instead of 4 in basic because you start counting at 1 instead of 0.

L1 is not a list in the traditional sense that we think of lists in Basic.  In Asm, memory is memory, there is no difference between pictures, sprites, and strings.  L1 is not a list, because Asm deals only with memory. L1 is a pointer. What that means is that in the calculator, there are places of memory that are unused, and that are free to be used my you, an axe programmer.  Each list pointer hold the location of these 'safe' places, and allows you to write and read to them.  For example L1 points to the locations know to asm programmers as 'SaveScreen'.  All we need to know is that its a 714 byte space of free memory to use It has essentially 714 element, each holding a single byte.  So to write to the first element, you would do:

:#->{L1}

because L1 represents the 1st element of the 'SaveScreen' chunk of memory.  To write to other locations in the PlotScreen, you would just add a number to the location.  Like to store to the 3rd, you would add 2 to L1.

:#->{L1+2}

EDIT: Ninja'ed

Does that make more sense?  The pointers readme in the documentation might help a bit if you are still confused.  And if I am wrong Quigibo, please inform me!

ok that actually helps a lot

opne last small question for me then i think i get most of it we con only count up to 255 in 1 byte of space right  or what can we store in 1 byte of space as that is a bit confusing as well X.x

alright that helps alot ty quigbo and builderboy

actually one more question how would i say read the ans var in a program for say i wanted to make a subroutine for a basic game ??

so i would put that in the program and it basically points to ans for me ?

lol thats ok

and ty that will help alot as i think i might use axe to help make a few simple and fast routines for crimson as it should be faster than doing it in basic

Hmm, that's interesting.
How would you access lists/strings/matricies? And how hard would it be to return a variable to ans?
Also I was wondering, since L1-L6 are pointers in memory, does that mean you can access all areas of ram? But by entering different values to call different areas?