Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!mcsun!unido!fauern!fauern!immd4.informatik.uni-erlangen.de!mlelstv
From: mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst )
Newsgroups: comp.sys.amiga.tech
Subject: Re: A desparate plea....
Message-ID: <588@medusa.informatik.uni-erlangen.de>
Date: 20 Nov 89 14:59:41 GMT
References: <13920003@hpfelg.HP.COM>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 18

koren@hpfelg.HP.COM (Steve Koren) writes:
>I need a way to execute programs that meets the following criteria:
>  1) I must be able to examine the return code from the command
>  2) I must be able to pass command line parameters to the command
>  3) I must be able to redirect standard i/o
>  4) The command must run interactively;
>  5) The command, if it in turn executes another command, must properly
>     look at the AmigaDos path.

On some early fish-disk there was a 'make'-program that uses the following:

It spawns a process that Execute()s a program. The make program itself
talks to the spawned process as it's console handler and writes commands
to the cli. I know it had a possibility to look at the program's return code.

				Michael van Elst

E-mail: UUCP: ...uunet!unido!fauern!immd4!mlelstv