On 22/12/2016 07:28, Marko Mäkelä wrote: > The execution appears to continue just fine with the GOTO statement, > with all variables intact. Why was the CONT refused? What would the > GOTO do differently from the CONT if we assume that the line consists > of a single statement? CONT continues executing the program after the last error. It only keeps one copy of where the last error occurred, which gets wiped out by errors in interactive mode. You can't CONT an error in interactive mode as it only has a single interactive command, which has now been replaced with CONT. Hence the error. It would seem logical to change error handling in interactive mode so that the CONT information wasn't overwritten, however there may be reasons why it had to work like that. Message was sent through the cbm-hackers mailing listReceived on 2016-12-22 10:00:02
Archive generated by hypermail 2.2.0.