Compiler feature request: having a "variable scanner" baked into Axe Parser (preferably with a toggle so it doesn't take time when you don't want it to) that keeps track of and shows the variables used in the project being compiled.

#ifdef and #!ifdef

I asked for these a while ago, and Quigibo's response was the →→ operator. Is was much simpler code-wise to implement and has a simpler syntax, and we agreed that most of the time you need to know whether a constant has been defined or not, it's so you can define it if it isn't.

Although I think it would be nice to have these more general constructs eventually, hopefully the current solution will work for now. I don't think I have the familiarity with the Axe project to pull off feature as rooted in the compiler as this yet, unfortunately.

If you haven't defined a static variable earlier, you can use →→ to store a constant into that static variable. It's ignored if the static variable does already have a value, so you can use it as kind of #ifdef sort of thing

My request is to move the interrupt table to 0x9200 (tableStuff) and out of L2.

Matrefeytontias, what would be the purpose of that? Adding a syntax for including label address as inline data seems like an extremely specific thing (one that I'm not even sure I can think of a use for).

Eventually I would like to allow for including any constant expression in the middle of an Asm() block, so you could do something like Asm((_LLabel)). But until such a feature is added, is there perhaps a way that you can do what you're trying to do without it?

Feature request: Somehow make it able to use more than 2 byte variables

That would be very hard to do, I would imagine. Axe is pretty much entirely built to work with 16-bit values. But just wondering, what kind of things would you want to do with 32-bit values?

add, subtract(, multiply, devide), display, compare

Substract and display are already present
But multiply, divide and compare are still missing

That would be very hard to do, I would imagine. Axe is pretty much entirely built to work with 16-bit values.

Don't try to tell me something is impossible for you, I won't believe you

But just wondering, what kind of things would you want to do with 32-bit values?

I can't even imagine all the physics Builderboy could do if he had the precision offered by 3 and 4 bytes.