Using recursive mutexes and condition variables?

I have a question regarding recursive mutexes and condition variables. Given a mutex created with one of the following attributes: DCE threads pthread_mutexattr_setkind_np( &attr, MUTEX_RECURSIVE_NP ); X/Open XSH5 (UNIX98) pthread_mutexattr_settype( &attr, PTHREAD_MUTEX_RECURSIVE ); What exactly is the behavior of a pthread_cond_wait() and what effect do "nested" locks have on this behavior? Do mixing recursive locks and condition variables make any sense?

This is largely achademic. However, I (like everyone else in known space/time) maintain an OO abstraction of a portable subset of Pthreads and would like to know the appropriate semantics. Since the advent of the framework (about 3 years ago) I have managed to avoid using recursive mutexes.

Unfortunately, my back may be against the wall on a few new projects and I may be forced to use them. They seem to be a real pain. And yes I promise this concludes my postings on cvs for the forseen future.

More.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.