The problem with looping on the input from named pipes is that after the first read you're left with an EOF for the second read1, so the loop exits. Subsequently you can't loop on a named pipe without working some serious voodoo (over-riding CORE::GLOBAL::eof()?). So this provides with many excuses to do dubious things such as using goto(), labels and (dum dum dum) infinite loops. Personally I'd go with an infinite loop opening the FIFO on each iteration, or take have a good long think about it. Good luck!
HTH

broquaint

1unless you have something writing faster than perl can read

In reply to Re: Active Munging via a pipe (code) by broquaint
in thread Active Munging via a pipe (code) by deprecated

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.