comment on

Is it advisable to use the Perl's fork() emulation in Windows in “production” code?

Personally, I'd say that you should not use Perl's Win32 fork emulation at all.

This not necessarily because of bugs in that implementation -- though I have no doubts they exist -- but because

that emulation is not complete enough to allow *nix programming paradigms to be ported to windows without changes
its actual behavior isn't well-enough (at all?) documented to allow for a set of rules to be written down about what will and won't work.

As is, the fork emulation creates expectations of portability that are simply not achievable. Better I think to simple say "do not use".

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

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.

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> <u> <ul>
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 intervention).
Want more info? How to link or How to display code and escape characters are good places to start.