You can, if you use std::condition_variable_any, which allows for any type of object that supports the Lockable concept. However, in the case of recursive mutex, you do have to ensure that the given thread has only locked the recursive mutex once, since the condition variable only will use the unlock method on the unique_lock once … Read more
The code from Michael Foukarakis is almost good but he initializes the mutex twice which leads to undefined behavior. It should just be: pthread_mutex_t Mutex; pthread_mutexattr_t Attr; pthread_mutexattr_init(&Attr); pthread_mutexattr_settype(&Attr, PTHREAD_MUTEX_RECURSIVE); pthread_mutex_init(&Mutex, &Attr); I actually use this code in production, and I know it works correctly on Linux, Solaris, HP-UX, AIX, Mac OSX and FreeBSD. You … Read more
Most of the time, if you think you need a recursive mutex then your design is wrong, so it definitely should not be the default. For a class with a single mutex protecting the data members, then the mutex should be locked in all the public member functions, and all the private member functions should … Read more
For example when you have function that calls it recursively, and you want to get synchronized access to it: void foo() { … mutex_acquire(); … foo(); … mutex_release(); } without a recursive mutex you would have to create an “entry point” function first, and this becomes cumbersome when you have a set of functions that … Read more
The difference between a recursive and non-recursive mutex has to do with ownership. In the case of a recursive mutex, the kernel has to keep track of the thread who actually obtained the mutex the first time around so that it can detect the difference between recursion vs. a different thread that should block instead. … Read more