in reply to Re: Interacting with the shell ( backticks, system(), open -| )
in thread Interacting with the shell ( backticks, system(), open -| )

Thank you. So piping the command to a filehandle should keep the find . -ls process open until <FP> is closed? Anyway, it makes more sense to pipe if it doesn't slurp everything up at once like assigned the command to an array.

I also responded to davido's reply above as to why system() is returning the output of the command, in addition to the exit status.

Replies are listed 'Best First'.
Re^3: Interacting with the shell ( backticks, system(), open -| )
by BrowserUk (Patriarch) on Feb 05, 2014 at 15:18 UTC
    So piping the command to a filehandle should keep the find . -ls process open until <FP> is closed?

    The external process is connected to your end of the pipe via one or two buffers, usually 4k or 8k each.

    When (if) those buffers fill up, the external process will be blocked when trying to add more output to the pipe and thus will have to wait until your program reads some of the data from your end of the pipe before continuing.

    If the external program produces less output than the combined size of the buffers, it will run to completion immediately and the output will wait in the pipe until your program reads it.

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom