Encountering a RETURN statement without a GOSUB active would cause the "RETURN without GOSUB" error in QB. Currently we do not handle this case and the return statement would just throw away an active call frame (in case of a simple RETURN statement), or read a value from stack and attempt to jump to it (in case of "RETURN " statement). Both would be incorrect, and would likely cause a crash.
Encountering a RETURN statement without a GOSUB active would cause the "RETURN without GOSUB" error in QB. Currently we do not handle this case and the return statement would just throw away an active call frame (in case of a simple RETURN statement), or read a value from stack and attempt to jump to it (in case of "RETURN " statement). Both would be incorrect, and would likely cause a crash.