Hi Lee,
> I have yet to find any documentation on the web that defines the order
> of return.
The order of return after fork(2) is defined as being not determinable,
i.e. correct code has to cope with either order or even simultaneous
return since another CPU might be brought it to run one of
On 07/07/15 12:46, alan buckley wrote:
The port I’m currently looking at uses pipe() and fork() to run a command
and communicates between the main program and an external program.
The main program itself fails with an invalid handle error from RISC OS, so
I thought I’d just check the pipe
The port I’m currently looking at uses pipe() and fork() to run a command
and communicates between the main program and an external program.
The main program itself fails with an invalid handle error from RISC OS, so
I thought I’d just check the pipe command and it doesn’t appear to be
working.
