🚀 go-pugleaf

I seem to be talking to myself a lot at the moment!

My current findings are thus...

I don't think there ever was an issue with __cdecl or __stdcall, I think 
it was more an issue of additional threads calling the DllEntryPoint 
multiple times which was confusing me.

I've encapsulated my initialisation code within the DllEntryPoint by 
checking for DLL_PROCESS_ATTACH and then my uninitialising / destructor 
code within the entry point by checking for DLL_PROCESS_DETACH when it's 
finally unloaded.  This works fine.

My issue regarding multiple instances of the DLL - I've since discovered 
that I can only load one instance of a DLL per 'process'.  Every time I 
load the dll using LoadLibrary, it simply increments a count within the 
dll .  I think this means that any globals within the DLL are shared 
within the calling process so I don't actually have a separate instance.  
To create, manage and use multiple instances of classes within the DLL, 
I need to create my own management code.  Is this correct?

For example, within my dll I have classes that declare TCP and UDP 
Client and Server engines.  Access to these components is through a 
defined interface.  If I want to create both a TCP and UDP Server, I 
would have to create two pointers internal to the DLL, one for managing 
the TCP object, and one for the UDP object.  

What I was trying to do before was declare one pointer per 'dll 
instance' that would access the 'instance object type' but because I 
can't create 'separate DLL instances', the pointer was being use to 
create one object, and then being used again to create the next object.  
Hence this didn't work!  

I think I've got it right?  Can anyone confirm this for me please?  
Remy?

Thanks,

Loz