Re: How about trying to code a QB64 interpreter, instead?

The QBASIC 1.1 interpreter is extremely handy for debugging.

The main advantage of an interpreter over a source debugger is that the interpreter will let you make some changes to the program while it is running.

A debugger has the advantage of letting you see how your compiled program is actually running.

I wouldn't mind seeing a QB64 interpreter, but actually, a lot of the new QB64 functionality I either don't use, or rarely use. Mainly, I use the new data types, and DECLARE LIBRARY. I occasionally use _DELAY and _LIMIT. I will start using _CONTROLCHR and '$CONSOLE. Most of the other features, I haven't used yet. When I get around to it, I need to try QB64's PLAY statement's multiple note support. I tried it when it first came out, in one of the demos, but my computer was too slow for it at the time.

My point is that there is only a subset of QB64, and even QBASIC, functionality that I actually use. There are probably a few dozen QBASIC keywords that I never use.

Regards,
Michael