I am so sorry! In a previous node, when I asserted
The threads cannot both hold the lock. One must sit in cond_wait() while the other is working.... I assumed that a native speaker would be able to correctly read this in context of the discussion thread. My message was not that a program may not have concurrently executing threads. Goodness gracious, no. The implication was that the sample code, as presented by ikegami, cannot have two of its lock-protected sections executing in parallel. Both while loops are protected (with the sole exclusion of an internal region inside the cond_wait() routine).
In retrospect, I may have made a misjudgment, especially in light of the misspelled /disingenous/ in the title.
In reply to Re^16: Threads sharing global variable (disingenous)
by Anonymous Monk
in thread Threads sharing global variable
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |