🚀 go-pugleaf

nuscss1@vms1.iscs.nus.sg (Vax BULLET-IN-Board SysOps) writes:

>In article <mills.721334453@dialup.athena.lkg.dec.com>, mills@athena.lkg.dec.com (George Mills) writes...
>> 
>>Borlands line of compilers are confusing !!!
>> 
>>IDE-W (Integrated development environment under windows)
>>IDE-D (Integrated development environment under DOS)

>	There is only one Borland IDE (BC.EXE), and it works for both DOS and
>	Windows apps. Also bundled with BC is Turbo C++ for Windows(TCW.EXE),
>	a windows-based IDE complete with menus and icons. What's the
>	difference ? Beats me. Everything I've tried that works under BC.EXE
>	compiles beautifully under TCW.EXE as well.

Actually, this is no longer the case; the difference was that the BC
IDE supported code optimization that Turbo C++ didn't; the Windows IDE
shipped with Borland C++ 3.1 supports all the optimizations which the
DOS IDE does.  Turbo C++ continues not to support these optimizations.
However, the IDE's for both Windows and DOS are shipped in the same package.

>>TD (Debuger for DOS under DOS)
>>TDW (debugger for Windows under DOS [not a typo, yes DOS])

>	no it isn't. try running TDW under DOS, and you'll get a 
>	"This program requires Microsoft Windows" error message. Despite
>	its full text appearence, TDW is a Windows apps, except that it
>	cannot be switched around like ordinary apps. 

>>Workshop (Dialog Box editor/Icon Editor etc.)

>> 
>>Borland C++ (for DOS) I'm not sure if this animal exists. If it does
>>it probably includes Turbo Vision.

>	it doesn't. As far as i know, there is only a BC++ with the
>	application frameworks, and another without. Both
>	support DOS and Windows programming.

The Application Frameworks includes both Turbo Vision for DOS, and
ObjectWindows for Windows.

Adam Elman
aelman@cs.stanford.edu