Win32 Perl processes already have an asynchronous, interprocess, queuing mechanism. Its called the process queue.

It is how the few signals currently implemented are done. Its great advantage over any other mechanism is that the system already delivers some signals this way. ^C, ^Break, asynchronous timers, etc. It could be extended to emulate (some) other signals. A good first step would be to not convert all but four signals, (BREAK, INT, QUIT & TERM), sent to a process, into untrappable, fatal ones.

How far you could go with emulating signals is an open question. On *nix, many of them are raised by the system itself. For example, it would be possible to have another perl process signal its parent (SIGCHLD) when it terminates. But it's extremely difficult to arrange this for any non-perl child process.

It might be possible to inject code into the non-perl child process, but only if the required privileges are available. In many cases they would not be, which makes for a consistency problem. Even when the privileges are available, code injection is hard to get right for arbitrary processes. And, in many cases it could be seen as a security risk that opened the door to abuse.

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.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Implementing signals for Win32 Perl using named pipes by BrowserUk
in thread Implementing signals for Win32 Perl using named pipes by Corion

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.