12-03-2024, 07:00 PM
run only (No exe) should create a temporary EXE to run and then delete it when it's finished. Its purpose is to just help keep your file folders clean, without clogging them up with EXE files that you don't really care about keeping around (like code snippets for testing from the forums and such).
I suppose there's always the chance that your system has a weird set of permissions assigned to it where you can write files (and create new ones), but not delete them, and that would defeat the "Run only (No Exe)" purpose.
But QB64 and QB64PE are both nothing more than translators that translate your BAS code into C code, and then we use the gcc compilers to make that an executable which is then ran. "Run only" just cleans up and doesn't leave that exe behind (No exe), once it's finished doing whatever it does for you.
I suppose there's always the chance that your system has a weird set of permissions assigned to it where you can write files (and create new ones), but not delete them, and that would defeat the "Run only (No Exe)" purpose.
But QB64 and QB64PE are both nothing more than translators that translate your BAS code into C code, and then we use the gcc compilers to make that an executable which is then ran. "Run only" just cleans up and doesn't leave that exe behind (No exe), once it's finished doing whatever it does for you.