In direct opposition to the BF interpreter, I give you the FALSE interpreter! (beta 0.7903) Written in TI-Basic, it has to be the fastest TI-Basic based language ever (except BF, but easier to write code for and read)

The official command set is:

arithmetic operations: +-*/_
Logical operations: =>&|~
Stack operations: $%\@ø
variables ops: :;
program control: []!?#
strings/chars ops: " '
and IOStream commands: .,^ß
What do these random symbols do?

I have currently implemented: +-*/_=>~:;.,[]! (replaced _ with (-), ; with ^r, and ~ with =\=)
Working on: #. I'll use w (that's the graphing variable)
I need good symbols to replace: &|$%\@ø and maybe ß (not sure what it really does)

EDIT: ' and " are fully functional, and ^ is mostly working. I decided to use ()'s for double quotes.

Oh, and sample code: (doesn't work in current release)
(Pick a numbar)0,':,^A:1 1:1 2:(Guess the numbar  )1 1:1 2:[0,':,^A^r=~[0,(Nope!)B^r!]?]B:B^r!0,(You win!)
...where ~ is the not equal sign

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

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.

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...

dim(L1) returns the dimensions of L1. so if L1 = {3,6,2}, dim(L1) = 3.

or do you mean axe?

Yeah I needed to know how big L1 is in Axe. Found it, tho. 712, if my math is correct.

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⁽³⁾

ok finally a meaningful post in this topic!
(I really love that smiley, if you couldn't tell)

Finally, I have happened upon a stable version of the interpreter (bug-free, except when you push random buttons with ^) and enough time to share it with you!

Gone are the days when you had to run everything from Str1!  Now you simply slap it into a program and select it from a menu when you run the interpreter!  Due to the need for a unique header, I have decided upon "<insert description here>" (including the < and >, but replacing the description with whatever else) You (or the person running your program) can quickly and easily access the description by pushing ALPHA while selecting your program from the menu.  This same header could easily be used to specify filename if I make a compiler, probably by inserting a comma or hyphen between the description and it.

So, to make a program run with this interpreter:
 the program has to start with <, and must have a > before any valid code. the stuff in between will be displayed when the user pushes ALPHA, so make it relevant. (there doesn't have to be anything)
 All whitespace is ignored, except with the ' and ( commands, and then it is outputted as spaces. Sorry.
 Comments, for now, can be in lowercase characters. The interpreter will ignore these.
 Don't do anything illegal like popping an empty stack, it'll crash. Don't leave the stack full either, it's bad manners

thus concludes my release of v.9469... oh yeah a screenie and the files

oh yeah I included example programs in the .zip