in reply to Re^3: Alarms with ActivePerl do not work properly (small modification)
in thread Alarms with ActivePerl do not work properly

Windows is really that broken?

I'm glad I don't use Windows then.

  • Comment on Re^4: Alarms with ActivePerl do not work properly (small modification)

Replies are listed 'Best First'.
Re^5: Alarms with ActivePerl do not work properly (small modification)
by BrowserUk (Patriarch) on Jan 13, 2011 at 07:12 UTC
    Windows is really that broken?

    Not broken just different. Ie. not POSIX. It is Perl's attempt to make the world look like POSIX that is broken.

    I'm glad I don't use Windows then.

    Kinda begs the question re: your involvement in this thread.


    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.
Re^5: Alarms with ActivePerl do not work properly (small modification)
by Corion (Patriarch) on Jan 13, 2011 at 18:01 UTC

    Basically, the proper approach on Windows would be either to use (OS) threads, one per handle on which to perform IO, or to use asynchronous IO with either callbacks or locks. The whole thing is not entirely unlike other mechanisms, but the mechanism used by Perl to implement select on Windows, namely, the select function of Winsock.dll, only supports (its own) sockets and not the various other handles that can be signalled on Windows.