|
|
|
| Keep It Simple, Stupid | |
| PerlMonks |
comment on |
| ( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I'm pushing undef into the queue with ... and I think this will cause thread to return: It will. Eventually. But there is no guarantee -- indeed it is most unlikely -- that all of the threads will: a) get a timeslice; b) receive the undef from the queue; c) act upon it and exit; before your main thread tries to join them. The whole point of join is that it waits for the threads to finish, thus ensuring that your main thread doesn't exit before your child threads are finished. It rarely makes any sense to turn it into a non-blocking operation by calling is_joinable before calling join. The are a few specialist uses for that, but in the case of your code it only guarantees that any thread that is slow to finish will not get joined before you terminate the main thread; hence the error message. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^5: What is the correct way to finish multithreaded program?
by BrowserUk
|
|