Date:	Wed, 28 Apr 1999 16:10:20 +0200
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id:	<199904281410.QAA17551@acp3bf.physik.rwth-aachen.de>
To:	mssmsoft AT my-dejanews DOT com (Maxximo)
Cc:	djgpp AT delorie DOT com
Subject:	Re: I have a question, and need some help...
Newsgroups:	comp.os.msdos.djgpp
Organization:	RWTH Aachen, III. physikalisches Institut B
X-Newsreader:	TIN [version 1.2 PL2]
Reply-To:	djgpp AT delorie DOT com

In article <7g6eqo$i6s$1 AT nnrp1 DOT dejanews DOT com> you wrote:
> In article <7g54u0$r65 AT newsops DOT execpc DOT com>,
>   "Joshua Tacey" <josht AT softhouse DOT com> wrote:
[...]
> > I need for the User to type in a path for the files to go into and then have
> > that path be passed as an argument to the program that the install program
> > must execute. I need for the Origional Program (The Install One) to keep on
> > running after the program it exec's is complete.

As was stated by someone else, the plain vanilla solution to this is the ANSI
Standard C function 'system()'.

> Your problem have two solution.

> In standard C, you must:
> 	-create a new process (son) with fork()
> 	-in the son code, call the exec..() function
> 	-in the parent code, call the wait() function

This, of course, is not 'standard C' at all. It's a 'Standard Unix'
(POSIX) idiom. The definition of standard C (the ANSI/ISO Standard C
definition) contains not a single one of these functions.

--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -