Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!elroy.jpl.nasa.gov!decwrl!pa.dec.com!shlump.nac.dec.com!sieras.enet.dec.com!wallis
From: wallis@sieras.enet.dec.com (Barry L. Wallis)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Borland C++ 2.0
Message-ID: <20708@shlump.nac.dec.com>
Date: 4 Mar 91 15:12:59 GMT
Sender: newsdaemon@shlump.nac.dec.com
Distribution: na
Organization: Digital Equipment Corporation
Lines: 35


In article <2814@sparko.gwu.edu>, timur@seas.gwu.edu (The Time Traveler) writes...
>In article <20624@shlump.nac.dec.com> wallis@sieras.enet.dec.com (Barry L. Wallis) writes:
>>
>>In article <25988@rouge.usl.edu>, pcb@basin04.cacs.usl.edu (Peter C. Bahrs) writes...
>>!>Is it just a C++ compiler that is win3 kernel callable? i.e. I can
>>!>call the sdk functions.  
> 
>>
>>It's the former. It uses the Microsoft WINDOWS.H file and you do the standard
>>Windows calls. Time to reinvent the wheel, I guess.
>>
> 
>Wait a minute .... Does this mean that I need to have Microsoft's
>Windows 3.0 SDK to compile BC++ Windows programs?  I thought that BC++
>came with everything I needed.
> 

Sorry for any confusion I might have caused. You need *nothing* else (except
documentation) to develop Windows 3.0 programs with Borland C++. I'm up to
chapter 3 in the Petzold book and everything works like a charm. I also tried
compiling *all* the Windows 3.0 example programs. They all compiled and ran
successfully (there is a minor bug in the TODO, but, who's counting). 

BTW, the only real documentation on Windows that BC++ comes with is in the form
of their on-line help library. I wonder if they licensed that from MS also, as
it is formatted differently (and somewhat poorly) than the standard Borland
help screens. 

--- 
Barry L. Wallis			USENET: wallis@labc.dec.com 
Database Consultant		Prodigy (don't laugh): DNMX41A
U.S. DECtp Resource Center	DECUServe: EISNER::WALLIS (not on the net yet)
Los Angeles, CA			"No one voted for me, I represent myself" 
---