Article View: comp.std.unix
Article #683Re: qfork()
From: John F Haugh II
Date: Fri, 28 Dec 1990 20:54
Date: Fri, 28 Dec 1990 20:54
24 lines
1695 bytes
1695 bytes
Submitted-by: jfh@rpp386.cactus.org (John F Haugh II) In article <16271@cs.utexas.edu> peter@ficc.ferranti.com (Peter da Silva) writes: >How about "executes any code that changes the state of the program". So, >for example: executing =any= code changes the state of the program. that's the whole problem with this restriction - how much code is too much. >At this point, unless I'm confused about legal interpretations of "qfork()", >the value of "child" is indeterminate. what is probably needed is a "spawn()" function (god, i never thought i'd advocate such a critter) which can be responsible for understanding the legalese. if the only thing you can do after "qfork()" is "exec()", why not merge the two steps into a single function? sounds like the only way to get it right anyhow. -- John F. Haugh II UUCP: ...!cs.utexas.edu!rpp386!jfh Ma Bell: (512) 832-8832 Domain: jfh@rpp386.cactus.org "While you are here, your wives and girlfriends are dating handsome American movie and TV stars. Stars like Tom Selleck, Bruce Willis, and Bart Simpson." Volume-Number: Volume 22, Number 47
Technical Details
Message-ID:
<16307@cs.utexas.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsqReferences:
<16066@cs.utexas.edu> <16271@cs.utexas.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsq From: jfh@rpp386.cactus.org (John F Haugh II) Newsgroups: comp.std.unix Subject: Re: qfork() Message-ID: <16307@cs.utexas.edu> Date: 28 Dec 90 20:54:07 GMT References: <16066@cs.utexas.edu> <16271@cs.utexas.edu> Sender: jsq@cs.utexas.edu Reply-To: jfh@rpp386.cactus.org (John F Haugh II) Organization: Lone Star Cafe and BBS Service Lines: 24 Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman) X-Submissions: std-unix@uunet.uu.net