Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!hsdndev!wuarchive!cs.utexas.edu!jsq
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.std.unix
Subject: Re: qfork()
Message-ID: <16271@cs.utexas.edu>
Date: 27 Dec 90 18:56:25 GMT
References: <16066@cs.utexas.edu>
Sender: jsq@cs.utexas.edu
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 26
Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman)
X-Submissions: std-unix@uunet.uu.net

Submitted-by: peter@ficc.ferranti.com (Peter da Silva)

In article <16066@cs.utexas.edu> lewine@cheshirecat.webo.dg.com (Donald Lewine) writes:
> I would propose replacing the phrase: "executes any code" with "calls
> any function defined in this standard or the C standard {8}"  I think
> that does what you mean.

How about "executes any code that changes the state of the program". So,
for example:

	static int child;

	child = 0;
	if(qfork() == 0) {
		child = 1;
		exec...;
	}

At this point, unless I'm confused about legal interpretations of "qfork()",
the value of "child" is indeterminate.
-- 
Peter da Silva.   `-_-'    "Eat hot digital death, mainframe scum!"
+1 713 274 5180.   'U`          -- Attack of the Killer Micros.
peter@ferranti.com

Volume-Number: Volume 22, Number 43