In sections 11.8.1 and 11.8.2, there seems to be a difference in the definition of a subprocess. The wait fork sections seems to define a subprocess as being only those child processes created by the calling process, whereas the disable fork explicitly includes all of the child's descendants. The wait fork statement is used to ensure that all child processes (processes created by the calling process) have completed their execution. Specifying wait fork causes the calling process to block until all its subprocesses have completed. and The disable fork statement terminates all active descendants (subprocesses) of the calling process. One could argue that a child of a child is also created by the calling process. But the real question is: is this difference intentional? I don't see why the semantics of a subprocess should be different for these two constructs. Dave David Rich Verification Technologist Design Verification & Test Division Mentor Graphics Corporation dave_rich@mentor.com Office: 408 487-7206 Cell: 510 589-2625Received on Fri Apr 7 11:29:24 2006
This archive was generated by hypermail 2.1.8 : Fri Apr 07 2006 - 11:29:49 PDT