|
Boost :
|
- Next message: Peter Dimov: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Previous message: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- In reply to: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Next in thread: Stefan Seefeld: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Stefan Seefeld: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
Howard Hinnant wrote:
> layer (and that has been my sense from the boost community as well: "I
> want boost + cancellation").
May I drop in an innocent (or blaspheming?) question?
Why do we want cancellation?
Which kind of cancellation do we want (if at all)?
Do we really need true async cancellation, or suffices to be able
to control a thread at certain (well defined) points.
Wouldn't 90% of the users be happy if they just be able to instruct
a thread to stop while it is in an (idling) wait loop without
need to resort to custom (boiler plate) IPC mechansims?
Roland
- Next message: Peter Dimov: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Previous message: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- In reply to: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Next in thread: Stefan Seefeld: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Stefan Seefeld: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk