This is for all assembly programmers who want to develop Axioms for Axe, you can post your questions, related bugs, and other concerns here.  Although I have not actually finished the Axiom feature, I have finished a template for the format I am most likely to use.  It is possible that there could be some very minor changes, but you will easily be able to compensate for those.  I just want to release this now so people can start writing their routines in preparation for this feature.

I included the SDK as well as an example Axiom that shows how some of the current functions could be written as Axioms.  Unfortunately, I realized that it will not be possible to redefine the token names as I was planning since the hook would take too long to search through the program to figure out which Axioms are used in that source and then search through those appvars every time a token is displayed in the editor.  The slowdowns would be too great especially for larger libraries.

Anyway, happy programming!

This shall be interesting. People, though, just need to remember that those are against the programming contest rules, though, so do not use them in your entry.

What if Quigibo finishes this in a reasonable time?
And: Will it be able to be a data container?
For example all maps:
MyMap:
       .db $00,$45
       .db $01,$FF


No, this can't be used in the contest because this is assembly code which is against the rules.  These are not the Axe libraries, these are the assembly libraries.

What about data containers? (Edited my previous post)

In addition, your idea doesn't make any sense.  How could you use an inline command to store data?  The regular methods for Axe data storage involves moving data to the end of the program and gives you a pointer but the assembly is inserted directly at the place you put it.  Its like saying you would rather use Asm(Data) to store your data instead of [Data] since both store hex values into the program.  The difference is that the first one executes the data and the later is just storage.  Although technically its possible to store data in Axioms, its much less efficient and requires difficult assembly to make it usable as data.  Such assembly would be against the rules anyway.

Excellent idea Quigibo. This will make possible endless addons to Axe Parser.

I read the Axiom should be an appvar. You just compile as a program and convert it to program on calc. CelticIII can be a solution.
But with an hex editor is as simple as editing the variable type byte to an appvar? Curious to know and for me is easier than installing CelticIII and learn the command usage.

A bit lost here: What is Axiom going to be? Is it a library for the Axe language or for ASM itself, and how would it be used? Sorry, I couldn't find any page describing it.

Quote from: Quigibo on June 27, 2010, 04:37:36 pm

Yes, turning it into an appvar is as simple as changing the program type byte from $05 to $15 and renaming the file with the extension .8xv instead of .8xp

Thanks for that tip. Can the former be easily done through CalcSys?

Yeah, you have to find the program in the VAT (press 6,1,1 from the main menu iirc). Select its entry and press Alpha+V. The hex editor should then be pointing directly at the byte to change

A bit lost here: What is Axiom going to be? Is it a library for the Axe language or for ASM itself, and how would it be used? Sorry, I couldn't find any page describing it.

It is a library for Axe Parser in assembly. In the Axiom you define what token will make use of an assembly routine coded into the appvar.
In the source code (Axe Parser) you use the token you assigned to a certain routine (tilemapper, math...) just like another command.
In the compiled program the assembly routine is included.

With this you don't need to make inline assembly because it is actually an addin into the Axe Parser compiler.
It has the advantage over inline assembly for readability and any casual coder won't notice he is using an assembly library, he just sent an appvar into his calc, read the documentation and uses it. Still breaks the rules to the contest because it would allow cheating with hand written assembly, but maybe in the future some contests will allow certain Axioms. (Axe Parser with Axioms)

Quigibo, you really know how to give cool names. (Axioms and Axe Hax) Where did the Axioms came from? It sounds a bit like Axe.