While Parrot may make some of that pain easier to deal with (alarm, for example, though it's got issues anyway once you're running with threads) I don't think you're going to see fork or alarm or whatever go away, and honestly I don't think they should. (And my platform of choice--VMS--doesn't fork, amongst other things)

It's kind of silly to neuter things so you get a lowest-common-denominator system. Making perl platform independent by taking things away just hurts the people who're on platforms where it does work. (And fork is really unlikely to be completely emulated on Windows, or any other non-unix platform)

In reply to Re: (Ask Perl 6: Win32) Re: Re: Re: Builtin Watchdog for a sub (or block) by Elian
in thread Builtin Watchdog for a sub (or block) by PetaMem

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.