(05-14-2023, 09:16 PM)Dimster Wrote: ... then it can't possible move the cursor in the IDE to the offending line it has just identified but if the IDE and EXE both reside together during the creation of the program, is there not a shadowing movement of the cursor in the IDE to follow the line pointer in the EXE?
What "shadowing movement"? You're confounding yourself with the fact the QB64IDE "shadows" its window while your program is being created. Then when the creation is done, it is run, apart from the QB64 IDE. They remain two separate programs that have nothing to do with one another. This is like using any other code editor and being able to give it a command to QB64 to compile a BAS file to an EXE file.
As I've said, either you need an interpreter like QBasic, or there has to be a special edition of the QB64 IDE with a debug mode that allows what you want. This "special edition" has to do something like pick up text written to "stderr" and expect the user's program to complain into "stderr" besides throwing a MessageBox. Then from that information from "stderr" or whatever the IDE could move the cursor to the line where it thinks the error occurred.
LOL ChatGPT isn't going to make anybody wiser, and it's not going to teach anybody how to be a better creator of applications.
Quote:If the EXE tells you "Out of Range on Line 12345", and you don't have QB64 installed on that PC, how's it going to load *anything* into the IDE? Even IF you do have a copy of QB64 somewhere on your computer, how's it going to load the BAS file to jump to that line? Lots of folks distribute EXEs without the source being attached anywhere with it.
This is emphasized when the user's program was created with QB64 Phoenix Edition v3.7, and the QB64 that is available somewhere else is an earlier version, or the "dot-com" or "dot-rip" version, or even before it hit v1.
Without source code, the program would have had to be compiled in debug mode to have a ghost of a chance to see source code lines. In "gdb" and even better if using Freebasic. I don't know if a program compiled by QB64 could cause "gdb" to show BASIC source code lines while stepping through the program. That was a convenient trick Freebasic has which made me a bit more willing to use "gdb".