27 Mar
2007
27 Mar
'07
4:52 p.m.
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.