$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Yuval Ronen: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Previous message: Yuval Ronen: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- In reply to: Yuval Ronen: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Next in thread: Glenn Schrader: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Glenn Schrader: "Re: [boost] Boost.Threads, N2178, N2184, et al"
Yuval Ronen wrote:
> Peter Dimov wrote:
>> The join2 functions illustrate another point where I believe N2178 is
>> superior to N2184: they expose the superior Windows join model at
>> the C++ level instead of the more limited pthread_join. It's trivial
>> to make an n2184::thread provide the same semantics under Windows,
>> but nobody would be able to take advantage of them portably.
>
> The Windows superior join model? Can you please explain what do you
> mean by that?
You can "join" a thread more than once, from several threads, and you can do
try/timed joins.
- Next message: Yuval Ronen: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Previous message: Yuval Ronen: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- In reply to: Yuval Ronen: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Next in thread: Glenn Schrader: "Re: [boost] Boost.Threads, N2178, N2184, et al"
- Reply: Glenn Schrader: "Re: [boost] Boost.Threads, N2178, N2184, et al"
$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-footer.inc");
?>