Axe automatically adds ending NULs to the end of strings.

Not always. It adds a zero when the string is followed by a → and when it is inside a Text command, but if you do this:
"String1"
"String2"
none of them will be null-terminated, you need to do that:
"String1"[00]
"String2"[00]
This can be useful when for example you need to put a @ in the middle your text data, you just have to write this: "mymail"[48]"gmail.com, where 48 is the hex for @ (note that the true hex is not 48, I put that number at random).

Quote from: DrDnar on December 22, 2012, 02:43:28 pm

The runprgm Axiom lets you convert an assembly/Axe program into an appvar, and execute it. The only difference between a program and an appvar is the type byte, so it was easy functionality to implement. Of course, the program is still copied to RAM and run from RAM. Executing an appvar in flash without coping it to RAM is just too much of a headache, due to both the need to change the execution permissions (requires unlocking flash), and the fact that the location would be variable and might cross page boundries. If you really want execution from flash, use an application.

The problem is that with that axiom I can't call functions that are not part of the appvar/the prog.

What do you want to do? If your main program is an application, the program you called can call functions in the application if you swap it back into memory. There's already an Axiom for that.

For those who wonder what this version of MEMKIT adds to the memkit bundled in Axe's zip, well nothing
But it uses a set of tokens that is compatible with Jacobly's TEXT Axiom

And Jacobly made (yet) another version of MEMKIT that sorts by alphabetical order, here

What would be the purpose of such a command? It's possible that I'm misunderstanding your request, but to me it sounds like you're asking for a command that doesn't attempt to create grayscale by combining the main and back buffer contents each frame, but instead only provides the grayscale "weighting" for each pixel by displaying the full main buffer twice for every time the full back buffer is displayed once. If this is what you're looking for, couldn't the affect be achieved in native Axe, like this?

DGInit()
...
DG()
...
Lbl DG
If C-1→C
DispGraph
Return
End
DispGraph(L₃)
Lbl DGInit
3→C
Return


I want to introduce my new Axiom.
It's for creating and managing arrays at random memory locations.
When you created a array you can easily add or delete elements.
There's also a routine to go through all elements with a callback function and delete elements by the return value of the callback function.
It's very useful for making games where you have to handle many objects (as bullets or enemies).

I attached the source and the compiled Axiom but sadly I haven't written a readme file yet.
(tokens are in the 'ZOOM' menu)
It's my first assembly project and I would be glad if someone helps me optimizing it 

So here is a first readme with an explanation of all the commands.

I plan to make a Length command and a Reset command that clears the list (array).

I see two things that I think are not right :

• MaxLength and the actual length of the array both take 1 byte. That's not enough in most situations. For example, in IkarugaX my bullet engine handles 192 bullets, and each bullet is an 11-bytes entry. 192 * 11 = 2112, which won't fit in 1 byte.
• I can't see any function to retrieve individual elements from an array ...

Also, IMO in LScanD you should just stop the scan instead of deleting the current element if HL ≠ 0.

Idea : add a map function to apply to the whole list a function, with a lambda for instance.
For instance if the Map fnctions returns the adress to r1. Struct : x, y, type
MAP(LIST, log(Pxl-On({r1}, {r1+2}, {r1+3}*8+Pic1))