From:	"Andrew Jones" <luminous-is AT home DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000217120344 DOT 21421C-100000 AT is>
Subject:	Re: <Damian Y> Re: It's back, but the ...
Lines:	14
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID:	<gUYq4.53837$45.2820058@news2.rdc1.on.home.com>
Date:	Thu, 17 Feb 2000 20:31:08 GMT
NNTP-Posting-Host:	24.42.120.18
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news2.rdc1.on.home.com 950819468 24.42.120.18 (Thu, 17 Feb 2000 12:31:08 PST)
NNTP-Posting-Date:	Thu, 17 Feb 2000 12:31:08 PST
Organization:	@Home Network Canada
To:	djgpp AT Delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Then please explain to me why do Watcom programs behave much worse on
> Windows than DJGPP programs.

Care to cite some examples?  I've had more problems with DJGPP compiled
executables than Watcom (it's why I switch back to wmake instead of DJGPP's
make).
More than likely it was sloppy code on the programmer's part.  I've run Watcom
compiled apps and games under Windows, and aside from a few regular problems
(Windows' fault), I've never experienced poorly behaved programs.

AndrewJ

- Raw text -