$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Howard Hinnant: "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: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
Howard Hinnant wrote:
> On Mar 27, 2007, at 12:35 PM, Peter Dimov wrote:
>
>> Once there, we may (or may not) opt to actually make the thread
>> object useful after detach because this pattern currently has no
>> other uses. This
>> leads us directly to the 'detach suppresses cancel but has no other
>> effects'
>> model, where you can still query the id of the detached thread,
>> among other things, if you hold onto the object for a while.
>
> What would join() do after detach() in this model?
What it always does. Wait for the thread to end, then return.
- Next message: Howard Hinnant: "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: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Howard Hinnant: "Re: [boost] Boost.Threads, N2178, N2184, et al"
$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-footer.inc");
?>