Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!uunet!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: HELP with Independant Children Processes
Message-ID: <18669@cbmvax.commodore.com>
Date: 7 Feb 91 19:41:58 GMT
References: <1991Feb7.001246.5257@maytag.waterloo.edu>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 24

In article <1991Feb7.001246.5257@maytag.waterloo.edu> giguere@csg.uwaterloo.ca (Eric Giguere) writes:
>In article <1991Feb6.190231.1116@jato.jpl.nasa.gov> jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson) writes:
>>	IMHO, System() and Execute() are gross, because of the overhead invol-
>>ved. It's not all that difficult to use LoadSeg() and CreateProc(). Besides
>>parameters can be passed to the child process via the tc_UserData field in the 
>>task control block. 
>
>One thing I'm not sure about, though:  does the parent have to remain
>running to eventually do an UnloadSeg() on the child process?  The AmigaDOS
>docs aren't too clear on that one... I would like to know.

	If you start something with CreateProc, yes, or the child must
explicitly unload itself (under Forbid()!)  If started with CreateNewProc,
(assuming a seglist and not an entry), you can tell it to unload the code
on exit.  For Execute() and System(), there no need to do anything (they
spawn a full shell).


-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)