Alice felt dreadfully puzzled. The Hatter's remark seemed to her to have no sort of meaning in it, and yet it was certainly English. "I don't quite understand you," she said, as politely as she could.
Due to INTERCAL's implementation of comment lines (see section 4.5), most error messages are produced during execution instead of during compilation. All errors except those not causing immediate termination of program execution are treated as fatal.
All error messages appear in the following form:
ICLnnnI (error message) ON THE WAY TO STATEMENT nnnn CORRECT SOURCE AND RESUBMIT
The message varies depending upon the error involved. For undecodable
statements the message is the statement itself. The second line tells
which statement would have been executed next had the error not
occurred. Note that if the error is due to 80 attempted levels of
NEXT
ing, the statement which would have been executed
next need not be anywhere near the statement causing the error.
Brief descriptions of the different error types are listed below according to message number.
FORGET
were misspelled F-O-R-G-E-R,
the results would probably not be those desired. Extreme misspellings
may have even more surprising consequences. For example, misspelling
FORGET
R-E-S-U-M-E could have drastic results.
NEXT
ing.
ABSTAIN
or REINSTATE
statement references a non-existent line label.
STASH
ed value.
WRITE IN
statement or interleave
($
) operation has produced a value requiring over 32 bits
to represent.
RESUME
statement
evaluated to #0
.
RESUME
statement instead of GIVE UP
.
The following error codes are new in C-INTERCAL:
COME FROM
statement references a
non-existent line label.
COME FROM
references
the same label.