Some more interpreter issues resolved. I just discovered virtually every command that has a procedure name as a parameter does not bother to check if the procedure exists at all. No error message or anything. Example:
ON ERROR GOSUB blah
This will run with no error message. Also if the procedure 'blah' does exist it cannot have a parameter list. The interpreter will ignore this also:
ON ERROR GOSUB blah
PROCEDURE blah(param&)
RETURN
It ends up just ignoring the commands completely and the built in error handler is called. This happens with EVERY/AFTER, TRON proc, ON BREAK GOSUB, and all the ON MENU GOSUB xxx commands as well. I've done some work on this so the updated runonly catches all these even where the procedure should not have parameters. It will now report 'too many parameters' in such a case.
No comments:
Post a Comment