QLiberator v3.42
Posted: Fri Jul 30, 2021 11:56 pm
Here is the latest QLiberator with Per Witte's update to the NEXT_TOKEN m/c routine
Enjoy ...
Enjoy ...
The part of the pointer things are disassembled from MK for me plus a little SB demo prgram.pjw wrote:Are the source code/disassemblies for them available anywhere?
Im not quite sure what you mean, Ralf, but if they are part of Q-Liberator I, for one, am interested.RalfR wrote:The part of the pointer things are disassembled from MK for me plus a little SB demo prgram.pjw wrote:Are the source code/disassemblies for them available anywhere?
If there is demand, I can put in here.
Back when I was doing the Qlib decompiler, I started disassembling 'run336mod' to try to work out what SuperBASIC functions it did.pjw wrote:On closer inspection, there is little point to disassembling Qlib_sys
as the toolkit consists of a post-assembly concatenation of all the
other user-side toolkits: Qlib_run, Qlib_ext, Qlib_bin, and Qlib_ovl,
and therefore it can easily be recreated from those components.
My guess is that Qlib_run could be tough to unravel, as thats where
some of Qlib's internal technology lies hidden. But most of the other
toolkits could probably be disassembled in a rainy afternoon.
The question then is What to do with them? One super idea is: Nothing!
Any better?
Thanks, Martin,Martin_Head wrote:<>
Back when I was doing the Qlib decompiler, I started disassembling 'run336mod' to try to work out what SuperBASIC functions it did.
I did not do a lot of work on it. And it's not much more than the original disassembly. But here it is.
run336mod.zip
Probably of most use will be the table around Lab10620
In the example of key code $2C, Which is LOG10(). It shows you how to work out that it is handled at Lab10A12
I have included a list of what the key code mean in the DelibKeys documents