int e l 8.1 ERROR MESSAGES CAN'T CONTINUE Program execution can be halted by either typing in a control-C to the console device or by executing a STOP STATEMENT. Normally, program execution can be resumed by typing in the CONT command. However, if the user edits the program after halting execution and then enters the CONT command, a CAN'T CONTINUE ERROR will be generated. A control-C must be typed during program execution or a STOP STATEMENT must be executed before the CONT command will work. PROGRAMMING If an error occurs while the MCS BASIC-52 device is programming an EPROM, a PROGRAMMING ERROR will be generated.
An error encountered during programming destroys the EPROM FILE STRUCTURE, so the user cannot save any more programs on that particular EPROM once a PROGRAMMING ERROR occurs. A-STACK An A-STACK (ARGUMENT STACK) error occurs when the argument stack pointer is forced "out of bounds." This can happen if the user overflows the argument stack by PUSHing too many expressions onto the stack, or by attempting to POP data off the stack when no data is present.
C-STACK A C-STACK (CONTROL STACK) error will occur if the control stack pointer is forced "out of bounds." 158 bytes of external memory are allocated for the control stack, FOR -- NEXT loops require 17 bytes of control stack DO -- UNTIL, DO -- WHILE, and GOSUB require 3 bytes of control stack. This means that 9 nested FOR -- NEXT loops is the maximum that MCS BASIC-52 can handle because 9 times 17 equals 153. If the user attempts to use more control stack than is available in MCS BASIC- 52 a C-STACK error will be generated. In addition, C-STACK errors will occur if a RETURN is executed before a GOSUB a WHILE or UNTIL before a DO, or a NEXT before a FOR. - 98 -