Thanks for your feedback, corion and sundialsvc4!

This is a updated proposal of changes.

Changes to pod/perlfunc.pod

Added at end of fork

On some platforms such as Windows, where the fork() system call is not
+ available,
Perl can be built to emulate fork() in the Perl interpreter. The emula
+tion is designed to,
at the level of the Perl program, be as compatible as possible with th
+e "Unix" fork().
However it has limitation that has to be considered in code intended t
+o be portable.
See L<perlfork> for more details.

[download]

Added at end of kill

On some platforms such as Windows where the fork() system call is not 
+available.
Perl can be built to emulate fork() at the interpreter level.
This emulation has limitation related to kill that has to be considere
+d,
for code running on Windows and in code intended to be portable.
See L<perlfork> for more details.

[download]

Changes to pod/perlfork.pod

perlfork

Added at the end of =item kill()

The process which implements the pseudo-processes can be blocked and t
+he Perl interpreter
hangs.

[download]

New section added before =head1 BUGS

=head1 PORTABLE PERL CODE

In portable Perl code, kill(9, $child) must not be used on forked proc
+esses.

Forked process are in Windows implemented as a pseudo-processes. 
To use kill(9, $child) on pseudo-processes is unsafe.
The process which implements the pseudo-processes can be blocked and t
+he Perl interpreter hangs.

The outcome of kill on a pseudo-process is unpredictable.
It depends on the timing in the Windows operating system.
Code that has worked, suddenly can fail, resulting in errors which are
+ difficult to find.

[download]

In reply to Re: Proposal how to make modules using fork more portable by Anonymous Monk
in thread Proposal how to make modules using fork more portable by Anonymous Monk

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.