Re: Asynchronously capturing output from an external program

Is there any reason you can't have the command for the first program direct it's STDOUT to a temporary file and then read that temporary file? That's a common way to address this situation.

Comment on Re: Asynchronously capturing output from an external program

Replies are listed 'Best First'.
Re^2: Asynchronously capturing output from an external program by Furple (Novice) on Nov 09, 2010 at 17:39 UTC
I'm doing integration tests (as I stated in the second sentence) and so I don't want to have to re-write any of the existing machinery. I only want to check to make sure that it does what it's supposed to do. Otherwise there are a number of less painful ways to do this. I'm not sure why piping the startup command for the first program to a file hadn't occurred to me. Although... as it turns out it looks like that doesn't capture all of it's output... strange.	[reply]

Replies are listed 'Best First'.

Re^2: Asynchronously capturing output from an external program
by Furple (Novice) on Nov 09, 2010 at 17:39 UTC

I'm doing integration tests (as I stated in the second sentence) and so I don't want to have to re-write any of the existing machinery. I only want to check to make sure that it does what it's supposed to do. Otherwise there are a number of less painful ways to do this.

[reply]