04-04-2025, 08:45 PM
i got very spoiled by the qb45 debugger. but none of my programs were very complex. all my games in the early 1990s used key on/off/stop interrupts. i didn't have a good experience with inkey$ while on basica. because ibm pc and work-alikes possessed a keystroke buffer. different from the function of many 8-bit computers with built-in basic.
i have never used the "debugger" in qb64. probably never will. the "g++" works very slowly already. i don't want to make it even slower. even on internal ssd. it's not going to catch that great bug i always develop in every program. which is a misplaced variable. or which should have had a better name. or round-off error because the type should have been double instead of _integer64.
highlight statement lines. i was the proud owner of power c compiler with source code for the libraries. a library called "multi-c" which faked multithreaded programs on a single-core processor. never got to use it. also with this thing called power ctrace. all from mix software from richardson, texas. the power ctrace was a debugger. needed to compile the program with "debug" symbols into an exe file. then run power ctrace with that exe file as data. it allowed the user to step through code, forward or backward. statement by statement, not necessarily line by line. what was irritating is that if the program ended run. if the user desired to continue watching things in the program. then it couldn't be done. power ctrace had to be started again with the same exe file.
the quickbasic debugger was positively telepathic compared to that, though.
i have never used the "debugger" in qb64. probably never will. the "g++" works very slowly already. i don't want to make it even slower. even on internal ssd. it's not going to catch that great bug i always develop in every program. which is a misplaced variable. or which should have had a better name. or round-off error because the type should have been double instead of _integer64.
highlight statement lines. i was the proud owner of power c compiler with source code for the libraries. a library called "multi-c" which faked multithreaded programs on a single-core processor. never got to use it. also with this thing called power ctrace. all from mix software from richardson, texas. the power ctrace was a debugger. needed to compile the program with "debug" symbols into an exe file. then run power ctrace with that exe file as data. it allowed the user to step through code, forward or backward. statement by statement, not necessarily line by line. what was irritating is that if the program ended run. if the user desired to continue watching things in the program. then it couldn't be done. power ctrace had to be started again with the same exe file.
the quickbasic debugger was positively telepathic compared to that, though.