自动锁定和解锁的模板类

This is a class that encapsulates the critical section. So it is more convenient to lock your resource accessed by multiple threads.

/// <summary> /// a class encapsulating the CriticalSection /// </summary> class CLock { public: /// <summary> /// the constructor /// </summary> CLock() { __try { ::InitializeCriticalSection(&m_criticalSection); } __except(EXCEPTION_EXECUTE_HANDLER) { assert( false ); } } /// <summary> /// the destructor /// </summary> ~CLock() { ::DeleteCriticalSection(&m_criticalSection); } /// <summary> /// the lock operation /// </summary> bool lock() { ::EnterCriticalSection( &m_criticalSection ); return true; } /// <summary> /// release the lock /// </summary> bool unlock() { ::LeaveCriticalSection(&m_criticalSection); return true; } /// <summary> /// try to get the lock /// </summary> bool trylock() { #if(_WIN32_WINNT >= 0x0400) return ( ::TryEnterCriticalSection( &m_criticalSection) != FALSE ) ; #else return false; #endif // _WIN32_WINNT >= 0x0400 } public: CRITICAL_SECTION m_criticalSection; }; /// <summary> /// the template of the lock which can automatically lock and unlock /// </summary> template< class T > class CAutoLock { public: /// the oringinal type of the lock typedef T LockType; /// <summary> /// the constructor /// </summary> CAutoLock( T& Obj ) : m_lockObj( Obj ), m_locked( false ) { lock(); } /// <summary> /// the constructor /// </summary> CAutoLock( T& Obj , bool Block ) : m_lockObj( Obj ) , m_locked( false ) { if( Block ) lock(); else trylock() } /// <summary> /// the destructor /// </summary> ~CAutoLock() { unlock(); } /// <summary> /// the lock operation /// </summary> bool lock() { m_locked = m_lockObj.lock(); return m_locked; } /// <summary> /// release the lock /// </summary> bool unlock() { if( !m_locked ) return m_locked; m_locked = false; return m_lockObj.unlock(); } /// <summary> /// try to lock /// </summary> bool trylock() { m_locked = m_lockObj.trylock(); return m_locked; } /// <summary> /// judge whether it's locked /// </summary> bool locked() const { return m_locked; } protected: T& m_lockObj; bool m_locked; private: CAutoLock(); CAutoLock( const CAutoLock<T>& Obj ); CAutoLock<T>& operator=( const CAutoLock<T>& Obj ); };

You should use this class as following:

CLock m_lock;//define it as a class menber variable in the class declaration //To use { CAutoLock<CLock> autoLock(m_lock); //sth to protected } 

The lock operation is excuted when constructing the lock object. If the code goes out of the range "{}", the lock will be destructed so that the unlock is excuted.

Here I want to stress the two reasons why to lock the resource: one is to avoid the conflict that two threads write the resource at the same time, the other is that one thread reads the resource while it's not desirable for another thread to write it so that the result read is uncertian.

Once I saw one of my colleagues use the lock as follow:(to be continued)

 ::EnterCriticalSection( &m_criticalSection ); std::vector<DATA_PARM>::iterator _it = m_ReadDataVector.begin(); ::LeaveCriticalSection(&m_criticalSection); //some assignment to the iterator

As you see, he protect the operation of retrieving the iterator, but there is no protect on the assignment. Whereas the assignment is also the operation that can arise the synchronized problem. So it's important to know exactly which resource to protect.