C / C++ / MFC

softwaremonkey wrote:

shared between several threads

softwaremonkey wrote:

using a mutex

softwaremonkey wrote:

At present, I only need to lock the mutex once before accessing all data members, then release the mutex

struct S
{
   S() { InitializeCriticalSection(&myDataLock); }
   ~S() { DeleteCriticalSection(&myDataLock); }

   void Lock() { EnterCriticalSection(&myDataLock); }
   void Unlock() { LeaveCriticalSection(&myDataLock); }

   int GetData() { Lock(); int i(data_); Unlock(); return i }
   void SetData(int i) { Lock(); data_ = i; Unlock(); }
private:
   // Don't want to be able to copy it...
   S(S const&);
   S& operator=(S const&);
   CRITICAL_SECTION myDataLock;
   int data_;
};

Stuart Dootson wrote:

I believe that if a thread has ownership of a critical section, it can request ownership again and it gets it without delay

softwaremonkey wrote:

This is true, but if we call lock() and unlock() within the Get/Set methods then we reliquish ownership

S s;
s.Lock();
s.SetData(1234);
s.Unlock();

Stuart Dootson wrote:

I should emphasise that I'm pretty sure that's how critical sections work

Stuart Dootson wrote:

I'd validate that belief before relying on it

led mike wrote:

Absofreakinlutly!! Of course fraking microsoft keeps hiding that information in the documentation[^]

johnjitu wrote:

IT WIL ESCAPE SHORT