Catching termination of child process and system() call

Norman Diamond diamond at jit345.swstokyo.dec.com
Fri Jan 25 13:29:50 AEST 1991


In article <14965 at smoke.brl.mil> gwyn at smoke.brl.mil (Doug Gwyn) writes:
>In article <1991Jan24.023750.19569 at tkou02.enet.dec.com> diamond at jit345.enet@tkou02.enet.dec.com (Norman Diamond) writes:
>>In article <YANG.91Jan23133130 at newyork.nff.ncl.omron.co.jp> yang at nff.ncl.omron.co.jp (YANG Liqun) writes:
>>>It should be wait((int *)0).
>>It should be wait((union wait *)0) in BSD.
>
>No, it's wait((int*)0) in all flavors of UNIX and POSIX.

No, it's wait((union wait *)0) in systems that implement the bogus attempt
that we all know about.

>"union wait" was a bogus attempt by somebody to give names to the
>subfields of the status word, but it was never a correct description
>of how wait() actually works

It's rather disorganized but wait() does actually work in the same
disorganized manner, on those systems.

>and has been repudiated by IEEE 1003.1.

I'm glad to hear that.  Unfortunately, some computers aren't running
IEEE 1003.1 yet.
--
Norman Diamond       diamond at tkov50.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.



More information about the Comp.lang.c mailing list