Newsgroups: comp.windows.ms
Path: utzoo!utgpu!watserv1!news
From: tom@mims-iris.waterloo.edu (Tom Haapanen)
Subject: Re: Developing Windows applications
Message-ID: <1991Jun27.095046.1561@watserv1.waterloo.edu>
Followup-To: comp.windows.ms.programmer
Sender: news@watserv1.waterloo.edu
Organization: University of Waterloo, WATMIMS Research Group
References: <1991Jun25.185037.13719@fs7.ece.cmu.edu> <1991Jun26.183552.10042@bronze.ucs.indiana.edu>
Date: Thu, 27 Jun 1991 09:50:46 GMT
Lines: 17

michael burroughs <burrough@bronze.ucs.indiana.edu> writes:
> I have used both the Microsoft SDK with Microsoft "C" compiler and the
> Borland C++ 2.0 compiler which comes with a complete Windows 3.0
> development environment.  There is no doubt about it, the Borland
> product blows the Microsoft SDK out of the water.

Borland C++ is "complete" except for:
	- Documentation (esp. Windows API reference)
	- Windows debugging kernel
	- Heapwalker
	- Shaker
I won't start a flame war on the relative value of the environments, but I'll
note that we have both and I still primarily use MSC/SDK.  Followups to
comp.windows.ms.programmer.

[ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ]
[ "i don't even know what street canada is on"               -- al capone ]