Crashing the TI BASIC interpreter

[Retrospect]

20 minutes ago, RXB said:

Yea crashing on purpose is not really all that unexpected.

Well your statement is logically true, but I myself, am curious .... for me, it's mainly because I want to  see what sort of stuff we can do if we get things past the Parser that normally picks things up.  

You sound like you think it's a bit dumb, but really it's just a curiosity.

[RXB]

5 hours ago, Retrospect said:

Well your statement is logically true, but I myself, am curious .... for me, it's mainly because I want to  see what sort of stuff we can do if we get things past the Parser that normally picks things up.  

You sound like you think it's a bit dumb, but really it's just a curiosity.

LOL I work in GPL the source code for TI Basic and XB so I am not at all surprised at all. 

[bfollett]

Maybe the "how to do it" is well known now, but back in the day, I stumbled across a bad line of code I accidently wrote in an extended basic program that would crash and drop you out of the Extended Basic environment into the standard TI Basic environment with the program intact.  You could list the program and you would see gibberish characters for any TI extended basic commands in the code and would error out when you tried to run it, but if the code only contained standard TI basic code it would run fine.  Sadly, I don't remember what the line of code was.  It was nothing special something like a divide by zero being passed to a standard ti basic command.  Does anyone today know of a way to do this.

[Fredrik Öhrström]

Try this:

Add line 1 and 2 below to your program.

Run and there is an error message and you have jumped from x basic to ti basic.

 

1 !@P-

2 CALL COLOR

 

However this does not work if you have the memory extension connected.