in reply to Re^4: fork - alarm - output
in thread fork - alarm - output
Only if the child prints less than a pipe's buffer's worth
That (conservatively), probably covers 85% of the uses of such code. Are you telling me that you don't see a relatively simple modification to cater for the rest?
I mean without resorting to forks & execs and no-blocks and selects and events&globals, state-driven spaghetti code?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^6: fork - alarm - output
by ikegami (Patriarch) on Jun 08, 2010 at 17:09 UTC | |
by BrowserUk (Patriarch) on Jun 08, 2010 at 22:22 UTC | |
by ikegami (Patriarch) on Jun 08, 2010 at 22:55 UTC | |
by BrowserUk (Patriarch) on Jun 08, 2010 at 23:02 UTC | |
by ikegami (Patriarch) on Jun 08, 2010 at 23:06 UTC | |
|