Signals were a very, very bad design choice from the outset. *nix would be better off if they could be discarded. They have no good place in modern, multi-tasking, multi-threaded, multi-cored operating systems.
I do think, though, that signals have some merits over the event kinds of IPC. One of the strongest merit would be the fact that it doesn't require an event dispatch loop running to catch the signal. They are delivered directly to the handler whenever it occure and this could save some timing and codes if used well.

In reply to Re^4: I know that signal handling isn't working well on win32, but how bad is it? by AGhoulDoingPerl
in thread 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.