|
Boost :
|
- Next message: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Previous message: Tobias Schwinger: "Re: [boost] [function_types] is_callable_scalar.hpp missing fromrepository"
- In reply to: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Next in thread: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Roland Schwarz: "Re: [boost] Boost.Threads, N2178, N2184, et al"
Howard Hinnant wrote:
> Fair point. Perhaps we should go back to a more fundamental question:
>
> std::thread t(f);
> ...
> t.cancel(); // Logically is this a const or non-const operation on
> the thread executing t/f?
I prefer to first ask "does it matter"? If you can't observe the cancelation
state of t and if you are assured that t.cancel is valid no matter what else
is going on with t, what difference does a const/non-const label make to the
external observer?
(Internally there is a flag being set, of course.)
- Next message: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Previous message: Tobias Schwinger: "Re: [boost] [function_types] is_callable_scalar.hpp missing fromrepository"
- In reply to: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Next in thread: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Roland Schwarz: "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