EmmBee wrote:We have a new version of QLiberator.
<>
Thanks EmmBee, for keeping Q-Liberator alive and kicking!
I should probably have mentioned this before, but I was only inspired
to look into the matter more sytematically due to your recent update.
The problem bothering me is that QLib refuses to compile my programs
containing hexadecimal or binary numbers!
Actually it turns out that it does. Here you can follow my doleful
path to enlightenment (Examples tested on SMSQ/E only):
SAVE ram1_test_bas
QSAVE
LIBERATE
Enter ram1_test_sav into the QLib console. Ensure 'Winds' is off.
Click 'Compile'
Error: Needs _wrk file - not a _sav
So RENAME ram1_test_sav to ram1_test_wrk and enter that name into the
console and compile.
Error: File not found
So RENAME ram1_test_wrk to ram1_test_bas_wrk and enter that name into
the console and compile.
Error: File not found
Alter the name to ram1_test_bas in the console and try again.
BINGO!
EXecute the resulting _obj file: You get the default, black SBASIC
daughter job window with 4660 printed in the top left corner, as
expected.
Now do a LIBERATE ram1_test_bas,
(Note the terminating comma!) It should compile fine, so EXecute
ram1_test_obj:
Now you get the same 4660 printed in white on red in the TLC of your
screen, which you can check is console #1 of QLib's default windows
(despite Winds being switched off).
My preferred method for QLib-compiling stuff is to use the first
method described (above, under the code): Make a change to the code,
QSAVE. Click Compile. Test. Repeat. But clearly that doesnt work if
the source code contains binary or hex numbers.
The simplest fix, to my mind, would be to allow QLib to compile _sav
files with hex and binary numbers directly. _sav files and _wrk files
are virtually identical. (Different by one byte?)