well, a bit of an update:

wow. so far, absolutely no crashes. Not even when I abused the stack (ie pushed something and didn't pop it, or tried to pop an empty stack⁽¹⁾) All I've got so far is bugs

Had a couple problems with inline numbers and numeric output. that fixed easily enough(and my numbers display as signed 16-bits with no extra padding!)

my () and ' commands so far only support 1-byte tokens. that'll just be annoying to fix.⁽²⁾

my ^ command is having fun A continuous scrolling 1 until you press a key, when it spits out garbage. I know one of the Fix commands fixes that (or part), but I still do want it to scroll down when it hits the bottom... (I think). Either way, the garbage reminds me of b_call(_puts) with a random hl, but I am using >Tok... (still does the garbage when i stopped it from scrolling)

getkey is the same numbers whether or not I use parentheses, right? cause alpha (48) doesn't seem to be working.

Also, I'm still using 0.4.5

Also, my strings are displaying vertically⁽³⁾

Huh, interesting. I've never heard of FALSE before. Honestly I've never understood esoteric languages or how they work or anything (Not that I've really tried though >.>)

Anywho, that's cool. It seems interesting. Good luck on it.

Thanks. I'll need it. Sure, its a stack-based language, but who would've guessed porting it to Axe would involve so many Asm(E5)'s and Asm(E1)'s?

Btw, anybody know dim(L₁) off the top of their heads? No current access to the documentation...

I'm not worried about ^T. I'm worried about the fact that {...} can cut off the end of a two byte token, and {...}^r can be one of three things:

 1: two one-byte tokens
 2: a one-byte token followed by the first half of a two-byte
 3: a two byte token.

I also need to know how much to increment my 'PC'... which is a pointer to the next token in the program string.

From a string, and so that I can interpret them.

as in:

If A=T+
Goto PL
End
If A=T-
Goto SB
End
...

Except not all of my symbols I need to check are 1 byte tokens.

ok I can avoid using it in calls (or just use 'pop de/pop hl/push de' etc), and using it to store/recall the Ans is exactly what I'm using it for.
Also, I'll have a counter so that I know how many items are in the stack at a given time. Also gotta avoid using it in the middle of routines. like no Output(0,0,Asm(E1)>Dec), that'll probably cause an error

EDIT: also, while I'm here, "Str1" is sufficient for a GetCalc( filename, right?

I have now implemented: +-*/_=>~:;.,[]!#ß\$ (replaced _ with (-), ; with r, ~ with =\=, # with i(imaginary), ß with ^o, \ with e(euler's constant), and $ with pi)
I need good symbols to replace: &|%@ø

I figured out what ß does, but decided it was useless in the current setup, and replaced it with a clrHome/cursor reset. Basically the same.

Due to speed problems, I think I'll add '.FALSEINT' to the beginning
You'll still have to run from an external string, though.

Screenshot of speed, and an attempt at the awesomeness of WFRNG. oh and the part where the numbers go faster is when I enabled warp mode on wabbit wow apparently wabbit maintains screenshot speed even in warp mode... but it runs a little slower on-calc.

Awesome!  I love these little mini languages Why is it called False?

Well, according to the author, its because that's his favorite truth value.

Sentry is a program That lets you password protect certain menus (Your choice of program, APP, and memory menu). It is actually pretty cool. I found ways around it though... Including manually typing "Asm(prgmSENTRY" to unlock it. After that, I started deleting Sentry after installing it because it set hooks in RAM, so it worked without the program

Couldn't you just archive it? all your shells are blocked, so you can't run it from there.