Fork won't work right 100% of the time on windows (or VMS, or MacOS, though it will on OS X) ever. It can't, and there's a limit to how hard it's worth trying. This is documented in the perlfork section of the manual, though whether you'd think to look for it is another matter entirely.
Whether alarm works on windows is up in the air. Whether it does depends on whether windows has interruptable system calls, which is the big place it's useful.
Perl has system-dependent behavior, and it's never claimed otherwise. A fair amount of stuff--pretty much everything feasable--is emulated in places where the base functionality's not native, but there's no 100% guarantee. That's not going to change, nor should it. Because of that, it's always a good idea to check the assumptions behind anything you read before trusting them implicitly. (A good rule of thumb generally)
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.