🚀 go-pugleaf

Hi Mr.Lebeau, Thank U for Ur reply!

Remy Lebeau (TeamB) wrote:
>> I cannot create that queue
> 
> Yes, you can.  Simply have main() call Application->ProcessMessages()
> in a loop for the lifetime of the process.

No I can't sorry, but I cannot modify the console application so much :( 
That is not my code, and it's not written for a Borland compiler at 
all:( Maybe it will be even compiled for Linux (So I should even find a 
way to make my clx code compile in Linux :( .. Check the other post into 
Socket group about indy and CLX )the other programmers r going to use my 
code through my dll. I can do whatever in my dll, but very few 
modifications to the console application...

> You don't.  Not from inside the DLL, anyway.  That is the
> application's responsibility.  Have the DLL call the callback in the
> context of the thread, and then the application has to make sure its
> callback is actually thread-safe.
> 
Ok. I've exported 3 functions from my dll:

bool TryEnterInThreadSafeCode()
{
  if(CritSectInit)
   return TryEnterCriticalSection(&CriticalSection);
  else
   return false;
}

void WaitForEnteringInThreadSafeCode()
{
  if(CritSectInit)
   EnterCriticalSection(&CriticalSection);
}

void LeaveThreadSafeCode()
{
  if(CritSectInit)
   LeaveCriticalSection(&CriticalSection);
}

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!)

Then I require the callback function inside the console application to be:

void OnAsynchReceiveCommand(char* Buffer)
{
  WaitForEnteringInThreadSafeCode();
  //do their stuff
  LeaveThreadSafeCode();
}

and anytime in the main thread they require to read memory used by the 
second thread

if(TryEnterInThreadSafeCode())
{
  //do whatever with shared memory
  LeaveThreadSafeCode();
}

All seems to work... is that thread safe?

Thanks again!

Stefano B.