Message120195
| Author | kristjan.jonsson |
|---|---|
| Recipients | georg.brandl, jyasskin, kristjan.jonsson, pitrou |
| Date | 2010-11-02.00:29:11 |
| SpamBayes Score | 4.217803e-06 |
| Marked as misclassified | No |
| Message-id | <1288657753.33.0.884410299435.issue10260@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Good points, Jeffrey. Documentation can be improved and cond.wait_for(pred) is indeed not guaranteed to wake up when predicate is true unless someone calls notifyAll. I spent some time thinking of a name. I tried wait_predicate and predicate_wait, but wait_for seemed natural. Any other ideas? How about wait_until_true? My original method had this as a free function, but I moved it into the Condition because I could see no other kind of primitive that would use it. I agree that it is unfortunate to pull what is essentially a utility function into the Condition variable, so I am leaning towards keeping it a module function. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-02 00:29:13 | kristjan.jonsson | set | recipients: + kristjan.jonsson, georg.brandl, pitrou, jyasskin |
| 2010-11-02 00:29:13 | kristjan.jonsson | set | messageid: <1288657753.33.0.884410299435.issue10260@psf.upfronthosting.co.za> |
| 2010-11-02 00:29:12 | kristjan.jonsson | link | issue10260 messages |
| 2010-11-02 00:29:11 | kristjan.jonsson | create | |