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.
>>
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 us
Hello,
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
documentation about this i found a stackove
3 matches
Mail list logo