I agree. It seems to me that retrying should be the job of a module, not that of builtins.

Mind you, the behaviour is not new. It dates back to at least Perl 3.

system also has this loop, but it doesn't warn.
fork does not have this loop.

Instead of hooking into the warning, you could use alarm.

Or you could avoid the issue completely by using open3 (since it wraps fork). 

my $pid = open3(*KID_TO_WRITE, '>&STDOUT', '>&STDERR', '-');
...
waitpid($pid, 0);

[download]

In reply to Re: Safe Pipe Opens and Implicit Loops by ikegami
in thread Safe Pipe Opens and Implicit Loops by martin

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.