Updated QB64PE 32-bit to the latest v3.2 to produce SICK64, on Windows10. I had a problem compiling the "analyze.bas". Maybe you used BASIC PDS v7.1 to come up with it, because it complains about "DIR$()" function. There is one in QB64PE but it behaves differently:
https://qb64phoenix.com/qb64wiki/index.php/DIR$
I guess you're prepared for it, otherwise this is going to be a PITA. Look what had to be done for Linux only to get anything that looks like Windows File Explorer in an user's QB64 program.
Another issue: the "sichelp.bas" is created successfully but when the user runs it and chooses option #6 it says it cannot find "syntax.doc". I noticed in the package the file was split into two parts because it was getting too big. This is only a functional bug which doesn't prevent EXE creation.
I composed a program on "SIC64" but forgot to put in line numbers. Loaded it in, ran it and did nothing. Maybe just after the user orders program run, make a quick syntax check such as using "VAL()" to make sure there's an integer line number at the beginning of a line? Some people might be put off by the stony silence or convinced the interpreter doesn't work. Although this stuff is for geeks anyway...
Maybe it's just my 10-year-old computer (Intel "Sandy Bridge" or near) but the interpreter reports incorrect CPU usage on its titlebar while waiting for keyboard input. I opened Windows Task Manager to discover it was only about 5% while the titlebar said 20% or more. It's something else that could dishearten a person who dives into things although could be middle-aged like we are around here. Another thing that could be considered confusing is this interpreter has a status bar, but the CPU usage and available RAM is displayed somewhere else in its program window.
I wish I had even more time to do useful things with this interpreter.
https://qb64phoenix.com/qb64wiki/index.php/DIR$
I guess you're prepared for it, otherwise this is going to be a PITA. Look what had to be done for Linux only to get anything that looks like Windows File Explorer in an user's QB64 program.
Another issue: the "sichelp.bas" is created successfully but when the user runs it and chooses option #6 it says it cannot find "syntax.doc". I noticed in the package the file was split into two parts because it was getting too big. This is only a functional bug which doesn't prevent EXE creation.
I composed a program on "SIC64" but forgot to put in line numbers. Loaded it in, ran it and did nothing. Maybe just after the user orders program run, make a quick syntax check such as using "VAL()" to make sure there's an integer line number at the beginning of a line? Some people might be put off by the stony silence or convinced the interpreter doesn't work. Although this stuff is for geeks anyway...
Maybe it's just my 10-year-old computer (Intel "Sandy Bridge" or near) but the interpreter reports incorrect CPU usage on its titlebar while waiting for keyboard input. I opened Windows Task Manager to discover it was only about 5% while the titlebar said 20% or more. It's something else that could dishearten a person who dives into things although could be middle-aged like we are around here. Another thing that could be considered confusing is this interpreter has a status bar, but the CPU usage and available RAM is displayed somewhere else in its program window.
I wish I had even more time to do useful things with this interpreter.