Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!sdd.hp.com!caen!kuhub.cc.ukans.edu!markv
From: markv@kuhub.cc.ukans.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: HELP with Independant Children Processes
Message-ID: <28411.27afc749@kuhub.cc.ukans.edu>
Date: 6 Feb 91 15:07:21 GMT
References: <1991Feb4.171549.28531@nntp-server.caltech.edu> <Jay.9138@deepthot.UUCP> <18606@cbmvax.commodore.com>
Organization: University of Kansas Academic Computing Services
Lines: 33

>>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. 
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~