You're going to kick yourself, I think...

By the time you use FH, STDIN consumed all the data in the file. I would have thought they'd have separate locations in the file, but I guess that doesn't make sense, since output dupes don't.

It works fine if you seek FH back to the start of the file, but then, you could just seek STDIN the same way:

open(FH,"<&STDIN") || die "Error with copying STDIN to FH : $!\n"; while ($inbuf=<STDIN>) { print $inbuf; } seek FH,0,0; while (<FH>) { print $_; } close(FH) || die "Error closing FH: $!\n"; exit;
Here it is with STDIN twice:
while ($inbuf=<STDIN>) { print $inbuf; } seek STDIN,0,0; while (<STDIN>) { print $_; } exit;
Both work fine.
--
Mike

In reply to Re: Duplicating STDIN by RMGir
in thread Duplicating STDIN by Leipzig

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.