🚀 go-pugleaf

Hi mr. Lebeau! Thank U!

>> The Critical Section is initializated in the Initialize function of
> my
>> DLL, and deleted in its Close function (the first and last the user
> must
>> call!)
> 
> You are going about this all wrong.  You are not responsible for
> providing thread-safety functions for the application to use.
> Especially if you are going to compile your DLL for other platforms,
> so you can't use platform-specific objects anyway.  The application
> has to manage its own thread safety on its own outside of your DLL.

Well I expressed myself badly :( ... On the console application I wrote 
a C++ unit (no BCB!) responsible of loading dynamically my DLL and that 
actually furnishes the interface for working with the DLL. So for 
example the initialize function on that unit calls the Initialize 
function on the DLL in Win32 way (LoadLibrary, GetProcAddress...) So in 
that function that is in the console application I can create the 
Critical Section. The DLL itself is free of that stuff, so it can be 
recompiled fine everywhere (please check my thread about CLX and indy in 
the socket group, I dunno what to do :( ).. The developer who will port 
  my code on another platform should only rewrite that small unit for 
loading the dll and its methods in a OS specific fashion.
So he can reinplement those functions EnterInThreadSafeCode and 
LeaveThreadSafeCode, in a specific way for his OS.
The DLL is free from that code :)
Hope thies way is correct.. I think I am doing what U say, cause only 
the console application is responsible for thread safe code, not my dll...
Thank You,
Best regards,
Stefano B.