Improved Error Messages for TI-Basic

Errors

Error Condition

New message

Error in condition statement (If/While)

A conditional statement did not resolve to TRUE or FALSE

NOTE: With the change to place the cursor on the line with the error, we no longer need to specify if the error is in an "If" statement or a "While" statement.

Missing EndIf

Expected EndIf but found a different end statement

Missing EndFor

Expected EndFor but found a different end statement

Missing EndWhile

Expected EndWhile but found a different end statement

Missing EndLoop

Expected EndLoop but found a different end statement

Missing EndTry

Expected EndTry but found a different end statement

Then” omitted after If <condition>

Missing If..Then

Then” omitted after ElseIf <condition>

Then missing in block: ElseIf.

When “Then”, “Else” and “ElseIf” were encountered outside of control blocks

Else invalid outside of blocks: If..Then..EndIf or Try..EndTry

ElseIf” appears outside of “If..Then..EndIf” block

ElseIf invalid outside of block: If..Then..EndIf

"Then” appears outside of “If....EndIf” block

Then invalid outside of block: If..EndIf


Syntax Errors

In case commands that expect one or more arguments are called with an incomplete list of arguments, a “Too few argument error” will be issued instead of “syntax” error

Current behavior

New CX II behavior

Note: When an incomplete list of arguments is not followed by a comma, the error message is: “too few arguments”. This is the same as previous releases.