Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!usc!jarthur!nntp-server.caltech.edu!tll From: tll@nntp-server.caltech.edu (Tal Lewis Lancaster) Newsgroups: comp.sys.amiga.programmer Subject: Re: HELP with Independant Children Processes Message-ID: <1991Feb6.170141.6422@nntp-server.caltech.edu> Date: 6 Feb 91 17:01:41 GMT References: <1991Feb4.171549.28531@nntp-server.caltech.edu> <18606@cbmvax.commodore.com> <28411.27afc749@kuhub.cc.ukans.edu> Organization: California Institute of Technology, Pasadena Lines: 45 markv@kuhub.cc.ukans.edu writes: >>>Under 2.0 you've got two choices: >>> System() >>> Execute() >It might be good to mention that Execute() is also available under >1.3. Also ANSI system() is available too. > >> Execute() under 1.3 or 2.0 is sync. >> And for compatibility, you can't get return codes :-( >> >> System() under 2.0 can be sync or async, your choice. And, if >> used sync style, you can even get return codes passed back from >> the program. >system() is sync also, but any such beast can be made Async by doing >someting like: > Execute("run foocommand", 0L, 0L); >Return codes are still a problem. And one can play games with >LoadSeg()/CreateProc(). >If you have Lattice/SAS you can also check into the fork() family, >which gives you some control over return codes, etc. >-- No thank-you!!! I implore you to stay away from SAS's fork() family until they have it fixed! I can show you a few lines of innocent looking code that will trash your hard-drive (or the disk of your cwd). It trashed my hard-drive 5 times before I track the problem to fork(). >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Mark Gooderum Only... \ Good Cheer !!! >Academic Computing Services /// \___________________________ >University of Kansas /// /| __ _ >Bix: mgooderum \\\ /// /__| |\/| | | _ /_\ makes it >Bitnet: MARKV@UKANVAX \/\/ / | | | | |__| / \ possible... >Internet: markv@kuhub.cc.ukans.edu >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Tal Lancaster tll@tybalt.caltech.edu