From:	"Campbell, Rolf [SKY:1U32:EXCH]" <moscoop AT americasm01 DOT nt DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	fork() should generate warning, Was (Re: DJGPP Setup Utility in the
	making.)
Date:	Wed, 09 Feb 2000 11:25:35 -0500
Organization:	Nortel Networks
Lines:	19
Message-ID:	<38A194FF.14FEB94B@americasm01.nt.com>
References:	<87jegs02e44 AT enews2 DOT newsguy DOT com> <389DAEE6 DOT 5B0550A5 AT tudor21 DOT net> <389EC8D9 DOT 1A02AA45 AT softhome DOT net> <jkut9s831tukb0jbcno5sj890i73ko3c0r AT 4ax DOT com> <389F175F DOT 9EC378DE AT softhome DOT net> <38A06E14 DOT 29AD52CC AT tudor21 DOT net> <38A176D2 DOT 75873E8F AT softhome DOT net>
NNTP-Posting-Host:	wmerh0tk.ca.nortel.com
Mime-Version:	1.0
X-Mailer:	Mozilla 4.71 [en] (X11; I; HP-UX B.10.20 9000/785)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Laurynas Biveinis wrote:

> Here comes one disadvantage that DJGPP has library
> functions like fork(), pipe() etc. which always fail.
> I moves meaningful error message from compilation
> to runtime.

    That's a good point.  I wonder why there isn't a compiler warning
for usage of 'fork' or any other UNIX functions that will always fail
under DJGPP.  I suspect it would make programs easier to port to have
the compiler point you to a line that will not work rather than hope
that the original program checks for error during fork and prints some
meaningful message.

--
(\/) Rolf Campbell (\/)

- Raw text -