The Sinclair QL Forum

tofro wrote: Tue Aug 19, 2025 5:23 pm And it wouldn't hurt if you don't as it apparently didn't bother anyone for the last 20 years.....

tofro wrote: Tue Aug 19, 2025 5:23 pm (It escapes my why someone would want to load SBASIC extensions into a daughter BASIC only - It maybe makes sense when you're developing an extension, but in "normal operation" it is likely just a good method to intensely confuse yourself)

Strangely enough, I do get asked (and usually refuse because I know what'll happen with endless support requests) to supply sources to my programs which install their extensions just in the SBASIC jobs in which they are run.

I happen to agree with you, but I know plenty who wouldn't.

It gets really confusing when people try to LRESPR system extensions like menu_rext locally into an SBASIC job and you have to explain it...

dilwyn wrote: Tue Aug 19, 2025 5:34 pm
It gets really confusing when people try to LRESPR system extensions like menu_rext locally into an SBASIC job and you have to explain it...

But that is definitly mentioned in the manuals.....

tofro wrote: Tue Aug 19, 2025 5:42 pm

dilwyn wrote: Tue Aug 19, 2025 5:34 pm
It gets really confusing when people try to LRESPR system extensions like menu_rext locally into an SBASIC job and you have to explain it...

But that is definitly mentioned in the manuals.....

Exactly.

I make these mistakes myself from time to time. But I try to learn from them, at least.

tofro wrote: Tue Aug 19, 2025 5:23 pm <>
And it wouldn't hurt if you don't as it apparently didn't bother anyone for the last 20 years.....

And Ive known about it these past 20 years. Awfully sorry I never mentioned it..

tofro wrote: Tue Aug 19, 2025 5:23 pm (It escapes my why someone would want to load SBASIC extensions into a daughter BASIC only - It maybe makes sense when you're developing an extension, but in "normal operation" it is likely just a good method to intensely confuse yourself)

I usually test unknown, "foreign" extensions in an SBASIC daughter job. Less chance of total system meltdown. Also to check and compare, etc. During development I always test my code in a daughter SBASIC.

 
https://superbasic-manual.readthedocs.i ... dix07.html
 
says in appendix A7.2.5 Loading Toolkits into an SBASIC

"This follows exactly the same rules as on a MultiBASIC."

And this is wrong! Please change this. For me the SuperBASIC Reference Manual Online is now the reference for stuff which is not in Jan Jones SuperBASIC's Definitve Handbook.
 

That chapter talks about "Loading Toolkits" - And yes, you're loading toolkits into SBASIC very much the same way as you load them into multiple Minerva BASICs - via LBYTES and CALL or LRESPR. I can't see what's wrong with that.

If someone writes me up a text file, with all the detail of how toolkits can be loaded into whatever systems --- SBASIC/SuperBASIC/MultiBASIC/Whatever --- you need, I'll convert it to the correct format --- ReStructuredText --- for the online SuperBASIC manual and get it uploaded.

I'm wondering a I should attempt to write a small utility, not necessarily in Assembvler, to convert plain text to the desired ReStructuredText format, to make life easier for everyone?

I did write a "how to" a while back https://github.com/SinclairQL/UpdatingS ... ter/source but I don;t see a PDF there ATM, so I'll need to chec k.


Cheers,
Norm.

tofro wrote: Mon Sep 01, 2025 11:29 am That chapter talks about "Loading Toolkits" - And yes, you're loading toolkits into SBASIC very much the same way as you load them into multiple Minerva BASICs - via LBYTES and CALL or LRESPR. I can't see what's wrong with that.

Because in a MultiBASIC (Minerva) they are resident to this (MultiBASIC) job (survive a NEW/LOAD) while in SBASIC not. I haven't had known this before this thread. This should be made clear in the Online Reference Manual (IMHO).