Brian Raven wrote: > > I don't think I was suggesting that Perl's alarm function works > identically on Win32 and Unix, that certainly wasn't my intention. My > main points were that the alarm function does exist on Win32 Perl, and
And my point was that it probably won't work on Win32. Pointing out that alarm exists, doesn't solve the problem of using it. > even if you were using Unix it probably isn't appropriate for a > multithreaded environment, both of which are contrary to what you wrote. I've never used Perl on UNIX in a threaded env but knowing UNIX in the past quite well, I doubt that true threads would hinder alarms. UNIX just doesn't do stupid things like that in their implementation. Either you would get one alarm per task and have to determine which thread to process it in or you would get one alarm per thread which would be much more useful. The one threaded UNIX I have used is SunOS and signals would be available by thread in that env. You could have one thread field the alarm signal and use another signal to then signal the correct thread that wants the interrupt (basically multiplex the alarm signal). _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
