From: Bruno Haible <haible AT ilog DOT fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15003.60532.423412.282631@honolulu.ilog.fr>
Date: Tue, 27 Feb 2001 19:05:40 +0100 (CET)
To: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
Cc: <djgpp-workers AT delorie DOT com>
Subject: RE: fork, pipe
In-Reply-To: <CAEGKOHJKAAFPKOCLHDIMEANCBAA.tim.van.holder@pandora.be>
References: <15002 DOT 41851 DOT 731838 DOT 645310 AT honolulu DOT ilog DOT fr>
	<CAEGKOHJKAAFPKOCLHDIMEANCBAA DOT tim DOT van DOT holder AT pandora DOT be>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Tim Van Holder writes:

> Yes - but that pertains to the decision to support DOS/Windows in the
> first place.  Also, it refers to the system in the sense of the available
> libc functions.  For example, DOS has no fork() or pipe(), so programs
> that require them would require extensive rewiring to work on DOS.

Modern Unix programs use 'posix_spawn' (declared in <spawn.h>) instead
of fork/exec when possible. I hope DJGPP implements this facility.

Bruno