On 1/17/07, Zbigniew <[EMAIL PROTECTED]> wrote:
But you might have more success arguing that "process" should not ever invoke a wait() call when you close its ports, and instead leave that up to the user. Since you receive the PID from "process", you can process-wait on it, and retrieve the error code yourself. This way, process does the dirty work of setting up and tearing down a new process and bi-directional pipes, while you can do the easy work of wait(). What do people think? Should the wait() be removed from process?
I think it shouldn't. The exit-status is a weak mechanism of communicating with the calling instance. Requiring a waitpid will just end up in unreaped child processes. If osprocess provides all the necessary things, users should prefer that for special requirements. cheers, felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
