in reply to Re: Checing presence of input on standard input in non-blocking way, sans user interaction
in thread Checing presence of input on standard input in non-blocking way, sans user interaction

"In other words, you want to be able to see if there's a reason to process input without stopping your program to wait for it. AND you want it to work even if the user had redirected input." -- marinersk

Indeed. My objective is to collect input from any & all of the ways, as in command | program.pl file < file2.

"Not sure why you wish to avoid using Term::Readkey but without that I would expect you to not find a solution." -- marinersk

It is not that I want to avoid use of T::R. I am|was curious if I might have missed something otherwise obvious to others (say on the lines of readline, sysread, select, tell, etc).

  • Comment on Re^2: Checing presence of input on standard input in non-blocking way, sans user interaction
  • Download Code

Replies are listed 'Best First'.
Re^3: Checing presence of input on standard input in non-blocking way, sans user interaction
by marinersk (Priest) on Jul 18, 2013 at 22:26 UTC
    Ah, understood.

    I will be watching this thread for awhile; if there is a procedure (or even a trick) out there for capturing this, I'd be interested in knowing it.

    Not holding my breath, mind you, but definitely interested.

    :-)