Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!letni!rwsys!spudge!johnm From: johnm@spudge.UUCP (John Munsch) Newsgroups: comp.windows.ms.programmer Subject: Re: Borland C++ 2.0 Message-ID: <28116@spudge.UUCP> Date: 4 Mar 91 16:16:07 GMT References: <1991Feb28.173016.22964@leland.Stanford.EDU> <1991Mar1.032721.20030@rti.rti.org> <2814@sparko.gwu.edu> Reply-To: johnm@spudge.UUCP (John Munsch) Distribution: na Organization: Friends of Guru Bob Lines: 24 In article <2814@sparko.gwu.edu> timur@seas.gwu.edu () 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. No. Borland C++ comes with everything you need to write Windows 3.0 programs. The ONLY thing it does not do that the SDK will do is allow you to create Windows Help compatible help files. I consider this a oversight and I expect it to be corrected by Borland. The original discussion was whether or not Borland included a set of class libraries to encapsulate the Windows functions or whether you had to create that yourself. John Munsch