On Fri, Dec 20, 2013 at 19:20, Ted Unangst wrote: > On Fri, Dec 20, 2013 at 17:48, sven falempin wrote: >> PTHREAD_COND_WAIT(3) is precise but easy to misread. >> >> It first say it will unlock the mutex given as a second argument, and after >> talking about the rest say it will be locked again. >> >> This second lock it supposed to have a particular usage, reading > > Learning how to develop a well designed threaded program is way, way > outside the scope of the pthread function man pages. I don't even want > to begin going down that road.
On the other hand, there are a lot of easy improvements to be made. For example, pthread_mutex_init doesn't have any references to pthread_mutexattr_init, which seems like an obvious entry for see also. The pthread_mutexattr_init man page is itself incomplete and doesn't document any of the possible values. Patches welcome (from anyone).
