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

Aha! Light dawns. This has the ring of truth about it. I hadn't appreciated the semi-permanent nature of these pipes.
Thanks!

Replies are listed 'Best First'.
Re: Re: Re^3: STDIN following on?
by dragonchild (Archbishop) on Aug 10, 2001 at 23:33 UTC
    You could try doing a close on STDIN, then re-opening it, but I have no idea if this'll work, or if it does, how well.

    ------
    /me wants to be the brightest bulb in the chandelier!

    Vote paco for President!

      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>