I know that signals are not working well on win32 port. But how bad is it?
I've read some article saying that it does still supported some, and I now wonder what signals are supported and what signals are not.

Particularly, I wonder about PIPE signal, which is triggered when you open a write pipe, but the other end of the pipe exits erruptly.
What would happen if the other end of the pipe got broken on win32 ports? Would it die out?, or fail silently?

Some of networking codes that I have been working on rely on the PIPE signal to be triggered at related event,
and that code is for the win32 environment. But if the $SIG{PIPE} is not working on win32, should I use eval on every piped writing?

Man, win32 sucks...:(

In reply to I know that signal handling isn't working well on win32, but how bad is it? by AGhoulDoingPerl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.