Re: IO::Select woes

You should explain in more detail what you expect. I am not surprised by the outcome: Your "piped" version reports reading from pipe data which indicates that can_read returned something with a true value. But then, you don't actually read from STDIN.

Comment on Re: IO::Select woes

Replies are listed 'Best First'.
Re^2: IO::Select woes by Anonymous Monk on May 04, 2023 at 15:39 UTC
Hi Haj, thank you for taking the time to review my issue and my sincere apologies for not being clear. The test script is the expected outcome and works as shown when reading from the pipe. My actual script ONLY enters the can_read() if clause when I am debugging. When my test script dumps the table to STDOUT, can_read() checks stdin (SHOWN), and after detected, I then plan to read the data within the if clause (NOT SHOWN).	[reply]

Replies are listed 'Best First'.

Re^2: IO::Select woes
by Anonymous Monk on May 04, 2023 at 15:39 UTC

Hi Haj, thank you for taking the time to review my issue and my sincere apologies for not being clear. The test script is the expected outcome and works as shown when reading from the pipe. My actual script ONLY enters the can_read() if clause when I am debugging. When my test script dumps the table to STDOUT, can_read() checks stdin (SHOWN), and after detected, I then plan to read the data within the if clause (NOT SHOWN).

[reply]