You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This reports an error ("cannot goto a nonexistant line"), but I think it should fall-through. Reporting an invalid line is probably the correct choice with:
10 PRINT "BLAH"
20 GOTO 3000
2000 PRINT "BLAH"
I guess here the expectation is that GOTO should go to the named line, and if it isn't present the next one that is there. But be limited by the upper-bound of lines that was used.
The text was updated successfully, but these errors were encountered:
Thanks for the issue! Haven't really thought about this mechanic to BASIC myself. Seems to be a great improvement, so I've created a pull request and I'm about to merge it!
Consider this program:
This reports an error ("cannot goto a nonexistant line"), but I think it should fall-through. Reporting an invalid line is probably the correct choice with:
I guess here the expectation is that GOTO should go to the named line, and if it isn't present the next one that is there. But be limited by the upper-bound of lines that was used.
The text was updated successfully, but these errors were encountered: