My "from PACKAGE import *" (Python) simulation project (reflection)

[ql_freak]

This is normal for SBASIC. It only loads new names into the name table which are actually being used in the child job, and then they inherit their properties from their ancestors in the main SBASIC.

Ah' didn't know that.

As for your extension not working, it's generally not recommended to load extensions in SBASIC child jobs, especially not when they contain system extensions such as device drivers and interrupt servers. They will be destroyed when you quit the child job but the system will still have hooks to them in system tables etc., which may crash the machine. It's better to load them in the main SBASIC.

My Reflection toolkit does not currently load any system extensions, just S(uper)BASIC FuNctions and PROCedures. It's practical to LRESPR them in a MultiBASIC job when developping. If you change something you can kill the MultiBASIC job, start another MultiBASIC, LRESPR the new version and test it.

QPC2 has some advantages over sQLux, e.g. the scrap (clipboard) which is shared between Windows and QPC2. And it supports German keyboard. BTW with UQLX (on Windows with an X11 server) the Geman keyboard is correctly working.

[tofro]

My Reflection toolkit does not currently load any system extensions, just S(uper)BASIC FuNctions and PROCedures. It's practical to LRESPR them in a MultiBASIC job when developping. If you change something you can kill the MultiBASIC job, start another MultiBASIC, LRESPR the new version and test it.

QPC2 has some advantages over sQLux, e.g. the scrap (clipboard) which is shared between Windows and QPC2. And it supports German keyboard. BTW with UQLX (on Windows with an X11 server) the Geman keyboard is correctly working.

The pragmatic way to develop an S*BASIC extension on QPC2 is:

Simply give the emulator enough memory and don't care at all about old versions hanging around - Whenever you have a new version, simply LRESPR it. With 256MBytes of memory given to QPC, you can LRESPR new versions a few hundred times for debugging before memory is exhausted. The new version will completely replace the old one in the system.

[Derek_Stewart]

This is normal for SBASIC. It only loads new names into the name table which are actually being used in the child job, and then they inherit their properties from their ancestors in the main SBASIC.

Ah' didn't know that.

As for your extension not working, it's generally not recommended to load extensions in SBASIC child jobs, especially not when they contain system extensions such as device drivers and interrupt servers. They will be destroyed when you quit the child job but the system will still have hooks to them in system tables etc., which may crash the machine. It's better to load them in the main SBASIC.

My Reflection toolkit does not currently load any system extensions, just S(uper)BASIC FuNctions and PROCedures. It's practical to LRESPR them in a MultiBASIC job when developping. If you change something you can kill the MultiBASIC job, start another MultiBASIC, LRESPR the new version and test it.

QPC2 has some advantages over sQLux, e.g. the scrap (clipboard) which is shared between Windows and QPC2. And it supports German keyboard. BTW with UQLX (on Windows with an X11 server) the Geman keyboard is correctly working.

If you load in the Extended Environment, (PTR_GEN, WMAN, HOTYKEY, QPAC2) this loads the SCRAP Thing onto any system that is capable of running QPAC2.

Systems like SMSQ/E, have the Pointer Environment (PTR_GEN, WMAN, HOTYKEY) built in. I am not sure if SCRAP is present till QPAC2 is loaded.

[RalfR]

I am not sure if SCRAP is present till QPAC2 is loaded.

The Scrap extension is part of Jochen's Menu-extension. The scrap menu is synchronized with the Windows clipboard using QPC_SYNCSCRAP.

[Derek_Stewart]

I am not sure if SCRAP is present till QPAC2 is loaded.

The Scrap extension is part of Jochen's Menu-extension. The scrap menu is synchronized with the Windows clipboard using QPC_SYNCSCRAP.

HI Ralf,

Thank you, for the clarification, so the definition of Extended Environment should include MENU_REXT.

I used to use QD on Minerva, but QD needs MENU_REXT to run, which implements the SCRAP extensions.

So is SCRAP a Thing or a device?

[RalfR]

So is SCRAP a Thing or a device?

SCRAP is an Extension Thing.