Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: HELP with Independant Children Processes Message-ID: <18638@cbmvax.commodore.com> Date: 6 Feb 91 23:31:11 GMT References: <1991Feb4.171549.28531@nntp-server.caltech.edu> <1991Feb6.190231.1116@jato.jpl.nasa.gov> <18637@cbmvax.commodore.com> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 21 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. Sure, if and only if you are certain it's code you wrote. If you need to execute an arbitrary or existing command, you need a proper environment. CreateNewProc can create such an environment, however it doesn't handle aliases, command paths, shell variables, internal shell commands, etc, etc. Use the appropriate tool for the appropriate job. System() is quite appropriate for a class of jobs, CreateProc/CreateNewProc() are appropriate for a different class. -- 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") ;-)