delorie.com/archives/browse.cgi | search |
Date: | Mon, 22 Feb 1999 15:44:13 -0500 |
Message-Id: | <199902222044.PAA08838@envy.delorie.com> |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
CC: | eliz AT is DOT elta DOT co DOT il, djgpp-workers AT delorie DOT com |
In-reply-to: | <199902221913.OAA17565@mccoy2.ECE.McGill.CA> (message from Alain |
Magloire on Mon, 22 Feb 1999 14:13:52 -0500 (EST)) | |
Subject: | Re: inetutils ? |
References: | <199902221913 DOT OAA17565 AT mccoy2 DOT ECE DOT McGill DOT CA> |
Reply-To: | djgpp-workers AT delorie DOT com |
> BTW, this merely a suggestion, I have no idea how spawn is implemented. unfortunately, spawn() is a sort-of standard, so we can't go around changing the parameters. If you're trying to implement fork(), you'll need to do the dup() in your fork code. > - When I spawn(), the parent goes on to its business right ? No. DJGPP doesn't allow concurrent processing. The parent waits until the child exits. > You kinda hinted that It may not be the case witout > something call "start /m". Windows supports concurrent processing, but dos (djgpp) doesn't.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |