in reply to IPC::Open3: differences among replies of a background process

but I now meet a problem on Windows

I don't use windows, but I do remember a few recent discussions of non-blocking pipe reads on win32. The problem is that win32 dosn't handle non-blocking pipe reads easily. See the replies way down in these nodes, Non-blocking Reads from Pipe Filehandle and Please suggest a non-forking way to do this (OS: windows) and especially ikegami's reply in Re: Please suggest a non-forking way to do this (OS: windows) (solution) for some techniques to get around it.

I'm not really a human, but I play one on earth Remember How Lucky You Are
  • Comment on Re: IPC::Open3: differences among replies of a background process

Replies are listed 'Best First'.
Re^2: IPC::Open3: differences among replies of a background process
by cramdorgi (Acolyte) on Dec 14, 2008 at 18:47 UTC
    Hi, Thanks for your reply, but so far, I don't do any non-blocking read: as long as I can handle stdout and stderr together, I can do blocking reads.

    I am afraid the other reply I got, from diotalevi, is correct: cleartool gets the user comments from an other device than stdin, and sends the prompt there as well.

    I tried to eliminate the other options (e.g. that the prompt would have been there, but with a carriage return hiding it, or that it would have been buffered and non flushed).

    I may have alternative strategies. Otherwise, I'll have to dig in the other APIs... OLE, and something called CAL.

    Thanks anyway,
    Marc

[reply]

In Section Seekers of Perl Wisdom