Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!think.com!mintaka!ogicse!pdxgate!eecs!dmatlock From: dmatlock@eecs.cs.pdx.edu (Delbert Matlock) Newsgroups: comp.windows.ms.programmer Subject: Re: Borland C++ 2.0 Message-ID: <1878@pdxgate.UUCP> Date: 7 Mar 91 01:57:53 GMT References: <1991Feb28.173016.22964@leland.Stanford.EDU> <1991Mar1.032721.20030@rti.rti.org> <2814@sparko.gwu.edu> Sender: news@pdxgate.UUCP Distribution: na Lines: 21 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... >>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. Actually, Borland licensed some parts of the SDK to include in BC++. All you need in addition to Borland C++ is a Windows programmer's reference manual if you want to write programs for Windows 3.0. ============================================================================= Delbert Matlock Internet: dmatlock@eecs.cs.pdx.edu MicroNet Northwest Voice: (503)228-3071