At 09:37 -0800 1/12/04, Stas Bekman wrote:
Elizabeth Mattijsen wrote:
You might also want to check out my Thread::Detach from CPAN:
Thanks, Liz. But the problem exists not only on Win32. I can easily reproduce it on linux.
Oh? That's news to me. I was under the impression the problem only existed on Win32.
Could you show me how to reproduce the problem on *nix?
% perl-5.8.3-ithread -le 'use threads; threads->new(sub { sleep 1})->detach for 1..1'
A thread exited while 2 threads were running.
So I don't think your doc is correct to say: "All of this happens on Windows only and if the version of the Perl executor is known to have the problem."
Well, to my knowledge it was... I've never had any problems with detaching threads.
of course ;)
In any case, for my test using join instead of detach does the trick just fine.
Yes, but some people prefer to be able to use detach() at one point in the future, hence my repair module. I thought it would just be needed on Win32. If it is needed on more platforms, I would like to know so that I can fix either the documentation and the internal OS checks.
Sure, but I have another workaround for my module and I don't want to create dependencies if I can avoid to.
Besides, I find it worrying that we have a flurry of workaround modules instead of trying to fix the core. Of course it's better than nothing, but it all should really be fixed in the core.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
