Thanks.
Sadly I just tried this and it doesn't work. The uninitialized value message is still there. Interestingly the error message is slightly different when this approach is applied to Cheeselord's example (which describes the problem well, I think). If I don't close and reopen STDIN, the string '<STDIN> line 6' is appended to the error message. Line 6 is where the first read occurs (i.e. where cat file | eoftest.pl feeds in). I wonder if these pipes are dictated by the parent shell rather than perl itself?

</musing>

In reply to Re: Re: Re: Re^3: STDIN following on? by tfrayner
in thread STDIN following on? by tfrayner

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.