05-14-2023, 07:34 PM
I'm not sure now but in the early days of QB64 when the IDE was opened it also opened "stdin", "stdout" and "stderr" files on Windows. This caused a problem with EXE files created by the program system that were burned to CD or DVD. However it might have written a runtime error message to "stderr". This was so it was picked up by a program like Geany or Notepad++ which was able to navigate to the line that caused the error. But that's for using an editor independent from QB64, and not the QB64 IDE.
LOL at pressing [ENTER] on the "MessageBox" of Windows. QuickBASIC/QBasic didn't show a dialog box when it wanted to complain about a runtime error, it simply stopped grinding, dumping an error message into the terminal. It wrote it into the graphics screen if it had to. Also it wasn't possible to "continue" running code although in QB64 in 99% of the cases it's useless or risky.
While using the Programmer's Workbench on BASIC PDS v7.1 and the program was compiled in debug mode, it was able to react to a runtime error by showing in the editor where it occurred. But this made the whole thing even slower than it already was, especially on any crappy disk made by Seagate such as what I was unfortunate enough to own.
Purebasic, something else that is payware could do the same thing. It even has a debugger independent from the Scintilla-based IDE, and a remote debugger that is less intuitive to use. I'm speaking about v4 primarily since I haven't used this product in years.
I'm saying that because QB64 would have to do the same thing. It might need a special version of the IDE to compile the user's program in a "detailed" debug mode. Then when the user's program is run and there is a runtime error, open that IDE to navigate to the line that triggered the problem. As Steve said, it's more like "LOL we're telling you where it is, just go find it and figure it out and fix it."
LOL at pressing [ENTER] on the "MessageBox" of Windows. QuickBASIC/QBasic didn't show a dialog box when it wanted to complain about a runtime error, it simply stopped grinding, dumping an error message into the terminal. It wrote it into the graphics screen if it had to. Also it wasn't possible to "continue" running code although in QB64 in 99% of the cases it's useless or risky.
While using the Programmer's Workbench on BASIC PDS v7.1 and the program was compiled in debug mode, it was able to react to a runtime error by showing in the editor where it occurred. But this made the whole thing even slower than it already was, especially on any crappy disk made by Seagate such as what I was unfortunate enough to own.
Purebasic, something else that is payware could do the same thing. It even has a debugger independent from the Scintilla-based IDE, and a remote debugger that is less intuitive to use. I'm speaking about v4 primarily since I haven't used this product in years.
I'm saying that because QB64 would have to do the same thing. It might need a special version of the IDE to compile the user's program in a "detailed" debug mode. Then when the user's program is run and there is a runtime error, open that IDE to navigate to the line that triggered the problem. As Steve said, it's more like "LOL we're telling you where it is, just go find it and figure it out and fix it."