Will a Global Var$ inside a DLL be different for all the Applications using the DLL simultaneously or shared between the Instances of the DLL? What about a Threaded Var$?
Another question: will a Global Var$ inside the Dll be available for multiple serial procedure calls? What about a Static Var$ inside the ProcedureDll? Will the Static Var$ inside the ProcedureDll be static for all Applications using the DLL?
And another: does a Threaded Var$ in a non-threaded environment fallback to Global Var$?
Thank you!
Global inside Dll
Global inside Dll
As you walk on by, Will you call my name? Or will you walk away?
Re: Global inside Dll
Each instance hate its own memory.
Thus Global, Threaded, etc. functions like in the main program.
PB-IDs like Windows, Images, Network have their own environment.
So it is not easy to create it from a DLL window and dialogs.
These must ALWAYS be created in the mainscope.
Thus Global, Threaded, etc. functions like in the main program.
PB-IDs like Windows, Images, Network have their own environment.
So it is not easy to create it from a DLL window and dialogs.
These must ALWAYS be created in the mainscope.
My Projects ThreadToGUI / OOP-BaseClass / EventDesigner V3
PB v3.30 / v5.75 - OS Mac Mini OSX 10.xx - VM Window Pro / Linux Ubuntu
Downloads on my Webspace / OneDrive
PB v3.30 / v5.75 - OS Mac Mini OSX 10.xx - VM Window Pro / Linux Ubuntu
Downloads on my Webspace / OneDrive
Re: Global inside Dll
No hate please!mk-soft wrote:Each instance hate its own memory.
Just kidding, I know you mean "Each instance has its own memory."
PureBASIC v5.41 LTS , Windows v8.1 x64
Forget UNICODE - Keep it BASIC !
Forget UNICODE - Keep it BASIC !