On Sep 3, 2008, at 7:58 PM, Paul Archibald wrote:
I do not have the source code to the subprocess, so I think I will
need to find another solution. I can't call setvbuf from my code,
can I?
I don't know about that - but: The documentation describes NSTask and
NSPipe and they have an exampl
I do not have the source code to the subprocess, so I think I will
need to find another solution. I can't call setvbuf from my code, can I?
I am using the TaskWrapper class from the Moriarity sample for my
task handling. It is pretty old, maybe it is not compatible with
Leopard or Xcode 3?
On Sep 3, 2008, at 12:03 AM, Paul Archibald wrote:
Okay, this has me stumped. Does Xcode somehow pipe the output of
the CLP to my app when it is present, and when its not there that
pipe is never "hooked up"?
It is your responsibility to establish the pipe between the
subprocess and your
Help.
I was about to send my client a new version of the app, and the main
thing I just thought I fixed has completely stopped working. Sheesh.
What the app does is launch a memory and cpu intensive command line
program and monitor its progress. It I run the CLP separately, I see
it outpu
