That would use the symbol table which is already limited by 153 entries for labels and static pointers.  If I add named constants, those would have to share that same space and also be limited to 3 characters long.  It would be nice though, I'll think about it.

By the way, a lot of people mentioned switch statements.  I tried before but I couldn't get much optimization.  But just now I remembered a better method for switch statements that was right under my nose the entire time: the same strategy I use already in the parser!  Each check would only take 4 bytes plus 8 bytes for initialization.  The format would be like this:

A->Switch(0,ZER,1,ONE,10,TEN,1000,THO)

Which checks A.  If A is 0 it jumps to ZER, if its 1, it jumps to ONE, etc.  And if its none of them, it continues.  This allows me to create a vector jump table for super space efficiency.  But, there is quite a lot of overhead, so this would be really only useful if you use it a lot.

ld   hl,(axv_A)
 ld   de,JT1
 ld   a,4
call JumpTable

JT1:
.dw 0,ZER
.dw 5,FIV
.dw 10,TEN
.dw 1000,THO

JumpTable:
 ld   b,h
 ld   c,l
 ex   de,hl
loop:
 ld   e,(hl)
 inc  hl
 ld   d,(hl)
 inc  hl
 ex   de,hl
 or   a
 sbc  hl,bc
 ex   de,hl
 ld   e,(hl)
 inc  hl
 ld   d,(hl)
 jr   z,done
 inc  hl
 dec  a
 jr   nz,loop
 ret
done:
 pop  hl
 ex   de,hl
 jp   (hl)


Sounds awesome!  I can't wait for switches.

I second the request for the #define command.

First that the Axe-specific entries in the catalog are implemented in the alphabetical order, so that tey're more easy to find.

I don't remember where, but I think someone asked for this before (I think it was somewhere in this thread). Quigibo said that it would actually be kinda hard. But I might be mistaken.

Second, that's actually a cool idea. But I'm not sure how easy that would be with hooks.
I know there is a parser hook, but I'm not sure what else there is.

Third, welcome to Omnimaga! You should introduce yourself in our introductions place/sub-forum/thing.

maybe a possible Lite-Axe program that compiles very simple programs on the fly O.o

Actually, that would be cool.  Kinda like how Dr. Java is a lite version of the real Java compiler.  Though, maybe someone besides quigibo should make this, he's already busy with normal axe

I think that the switch idea as it shows sounds really cool. If you are concerned about overhead for a lot of these commands, start eating into saveSScreen or appBackupSScreen if you aren't already. You could even create an Appvar buffer if needs be.

Quigibo doesn't have to do this, but I think it would be cool if someone made an app kind of like TI 83 Plus Catalog Help, except with Axe commands instead of TI-Basic. (As a review, this program installs a keyhook to the (+) key that brings up the command syntax for that command highlighted in the Catalog or function menus, and then lets you edit it in the top line and paste it back in the previous location). This would help people code using commands they don't usually use.

Quote from: ztrumpet on February 03, 2011, 06:27:18 pm

Sounds awesome!  I can't wait for switches.

I second the request for the #define command.

What would it do?

Defines stuff.  No, seriously, it just defines stuff as existing.  It's a strange command, to me.  It has some interesting uses, though.

Like if you didn't want to remember a number like E848E, you could #define a name for it.

Like #Define($848E, SAUSAGE), so that SAUSAGE = $848E

I got a random idea this morning--4*4 sprites.  Instead of it always having to be 8*8 and doing, say, [F09090F000000000], something like [F99F] would be just a square, and only a square.