Elizabeth Mattijsen wrote:isn't one the alias of the other?I guess I could implement this in my test script using a simple semaphore (shared variable), making sure that all callbacks pull down that semaphore just before they are done and having the main thread block till that semaphore gets to 0. e.g. your Running implementation could drop the other dependencies list and just override threads::create to wrap it in a semaphore up and down calls around the callback.Indeed. Don't forget that you need to steal threads::new as well ;-)
Yes. But if you steal "create" like:
*threads::create = sub {};
then threads::new is still pointing to the old, unwrapped sub. This caught me off guard with Thread::Exit as well, as the CHANGELOG will tell you... ;-)
Well, and that's exactly the conundrum: any work done on threads may well only appear in blead (and not in 5.8.4). How many people use blead on production systems?I remember sky saying that threads.xs will be released on CPAN. oh was I dreaming
No, he did say that. ;-)
"If you want to block until all threads have finished, you will have to do it yourself" was Jarkko's decision.OK, I didn't remember that. In which case threads should have running() or similar, but not call it by itself.
??? You mean, threads::running should exist by default in threads:: ?
Liz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
