He means like DispGraph.  The code for dispgraph is say 100 bytes, so to save space Axe puts it at the bottom of your program, and whenever you use DispGraph in your program, it calls it (kinda like sub()) from the bottom to save space

For a more technical reason why the parser works this way, I'll explain how each pass in the parser works:

First, the entire program is parsed EXCEPT for data and AxCalls.  Whenever it encounters an AxCall, it writes a "call XXXX" to the executable and moves on because the actual location of the routine can't be determined until the size of the executable is known.  Same with data.  If you used Str1 somewhere in your code it will replace the value of that pointer with XXXX as well and just continue as if nothing was wrong.  By the end of the first pass, the program is completely parsed but with a bunch of holes that need filling.

Then, the second pass happens.  The compiler does exactly the same thing, but in exactly the opposite way.  It scans through the program and anything that is not an AxCall or data is ignored (since it was already written in the first pass) but when it encounters one of these holes, it can now add that data/routine to the end of the program since we know where that is now.  It then takes the address of that location it just added and uses that to fill in the XXXX with the correct value.  It does this until the entire program is parsed and the compiling is complete.

That's why it would be difficult to add the AxCalls before the data, I would have to change the 2nd pass to only fill in the AxCalls and then add a 3rd pass to only fill in the data and tack that on to the end of the program.

Ah right, I guess it's better to leave things as they are, then X.x. I wouldn't mind longer compiling personally, but on a regular 83+ it might be a bit too long

It's not long on a plain 83+ either, especially now that Axe actually quits right after compiling. But whichever's easier, Quigibo.

maybe this could be changed for 1.0? it would definitely be worth any extra time.
then again, if it's too much work for you that's perfectly fine.

Yeah we don't want Axe to end up being like one entire page larger just because of this

Maybe in the future there could be  Axe Parser Lite and Axe Parser Full, though.

Yeah that's the main issue

It was hectic to update ROL series because there's a french and english version for each game.