QPC2 MultiBASIC: Load SBASIC machine code function resident

[dilwyn]

And it wouldn't hurt if you don't as it apparently didn't bother anyone for the last 20 years.....

(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...

[tofro]

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.....

[dilwyn]

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.

[pjw]

<>
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..

(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.