Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucsd!helios.ee.lbl.gov!nosc!logicon.com!trantor.harris-atd.com!trantor!dsampson From: dsampson@x102a.harris-atd.com (sampson david 58163) Newsgroups: comp.windows.ms Subject: Re: Borland C++ with Windows 3.0? Message-ID: Date: 5 Jul 90 13:48:45 GMT References: <604@cvbnetPrime.COM> Sender: news@trantor.harris-atd.com Organization: Harris Gov't Aerospace Systems Division Lines: 70 X-Local-Date: 5 Jul 90 06:48:45 PDT In-reply-to: jshekhel@feds19.prime.com's message of 2 Jul 90 21:59:40 GMT In article <604@cvbnetPrime.COM> jshekhel@feds19.prime.com (Jerry Shekhel ) writes: >Does anyone know whether Borland C++ is capable of producing Windows >3.0 applications if used with the SDK? Also, can the Borland >debugger, which supports hardware traps on the 386 be used to debug >Windows programs? The current version of Turbo C++ does not allow you to use the SDK to write windows 3.0 programs. Somebody please tell me I wrong :). I see nothing in the current documentation that specifically states that you can link to the SDK libs and use Link4 [the SDK supplied linker] to produce windows compatable programs. While Borland has made press statements that they were going to support that environment, we'll all have to wait for the next release of C++ to do that. The intresting thing about all of this is that Borland began shipping Turbo C++ the week before Microsoft put on the big blitz show for Windows 3.0. I read in PC Week that Borland was one of the vendors at the show and that they were demonstrating the next version of Turbo C++ that ran under windows (editor and all) and it produced Windows 3.0 compatable code. Since Borland is very busy selling the current version of C++, I'd expect them to sit on this next release until late fall (Nov - Dec) at the earlist before announcing the product they demonstrated at the MS Windows show. After all, why should they sabatoge sales of their own product. Of course, they could create "parallel" C++ products: windows and non windows versions. But they haven't said anything publicly yet other than they will support the windows environment. Personally, I'm anxiously awaiting the Borland product. I really don't like the MS C environment for developing applications. The MS C compiler is very powerful, but I have run into problems. I have the SDK for windows 2.xx. To run Codeview, you must install an expanded memory driver. So I installed the driver that was shipped with my Gateway 2000 20MHz 386. Once that was loaded, Windows 3.0 wouldn't fire up. I got a message box that saying that another driver was conflicting with the memory that windows wants to use, blah, blah, blah..... So I unloaded the expanded memory driver and tried to run Codeview as a window in 386 mode, figuring that windows is so smart now, it will manage the memory for me :). Well Codeview complained that it needs an expanded memory driver before it can load. Catch 22. So now I have to put print statements in the code to see what's happening, which is almost useless as a debugging aid. I ordered the SDK for windows 3.0. Man, I hope this hassle goes away!! You can appreciate why I am prejudiced in a positive way towards Borlands environment. Part 2 of your question about the debugger, I'll claim ignorance on. I've never tried playing around with it in that fashion. I will say that unlike Codeview, Borland's debugger is highly intutive. I've had various versions ever since it came out about 2 years ago (I've upgraded each time). I still haven't had to read the manual yet to do the things I wanted to do. Now that's a well designed, user friendly program! David -- ------------------------------------------------------------------------------- David Sampson Harris Corporation dsampson@x102a.ess.harris.com Gov't Aerospace Systems Divison uunet!x102a!dsampson Melbourne, Florida -------------------------------------------------------------------------------