From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Missing C++ keywords...in RHIDE (?)
Date:	21 Sep 2000 11:57:07 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	27
Message-ID:	<8qct2j$gel$1@nets3.rz.RWTH-Aachen.DE>
References:	<01c0235d$5c8ab9e0$db0d1ad8 AT rlatiola>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 969537427 16853 137.226.32.75 (21 Sep 2000 11:57:07 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	21 Sep 2000 11:57:07 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Lord Williams <lordwill AT teleport DOT com> wrote:

> I dont know why but I cant find the syntax or index help for
> finding:

The reason why is that these are features of the C++ programming language,
which you're supposed to learn from some textbook. It's in no way specific
to DJGPP as a compiler, so there'd be little point in DJGPP carrying the
documentation for it.

> And theres no MSDOS impementation of child processes mentioned in
> the documentation. 

MSDOS is not multitasking-capable, i.e. *has* no concurrent child
processes, so there's little we could do about that.

> if I wanted to port over a UNIX program using fork() what would I do
> to create a child process that would make up for that problem?

fork() alone can't be implemented on DOS.  But the usual combination
of fork() with exec() and wait() for doing a non-concurrent subprocess
is equivalent to a spawn() on DOS. If your Unix source is trying to
run a child process concurrently, you'll have to change it
fundamentally. The DJGPP FAQ has something about this, too, IIRC.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -