Borland C++ is a C and C++ IDE
(integrated development environment)
for MS-DOS and Microsoft
Windows. It was the successor to Turbo
C++, and included a better debugger, the Turbo
Debugger, which was written in protected
mode DOS.
(integrated development environment)
for MS-DOS and Microsoft
Windows. It was the successor to Turbo
C++, and included a better debugger, the Turbo
Debugger, which was written in protected
mode DOS.
Object Windows Library (OWL): A set of C++ classes to make it easier to develop
professional graphical Windows applications.
professional graphical Windows applications.
Turbo Vision: A set of C++ classes to create professional
applications in DOS. Those classes’ mimics some of the aspects of a Windows
application like: dialog boxes, messages pumps, menus,
accelerators, etc.
applications in DOS. Those classes’ mimics some of the aspects of a Windows
application like: dialog boxes, messages pumps, menus,
accelerators, etc.
Borland Graphics Interface: A library of functions for doing simple,
presentation-style 2D graphics. Drivers were included for generic CGA, EGA and VGA capability,
with support for a limited number of video-modes, but more advanced,
third-party drivers were also available.
presentation-style 2D graphics. Drivers were included for generic CGA, EGA and VGA capability,
with support for a limited number of video-modes, but more advanced,
third-party drivers were also available.
Borland Power Pack for DOS: Used to create 16- and 32-bit protected mode DOS
applications, which can access a limited scope of the Windows API and call
functions in any Windows DLL.
applications, which can access a limited scope of the Windows API and call
functions in any Windows DLL.
Borland Code Guard: Once installed and integrated within the IDE, Code
Guard can insert instrumentation code in the final executable that can be used
to monitor: pointer usage, API calls, how many times some
function is called, and other features. If some error is found, a pop-up window
appears, the debugger can stop, or a log is written to disk.
Delivered for 16- and 32-bit applications.
Guard can insert instrumentation code in the final executable that can be used
to monitor: pointer usage, API calls, how many times some
function is called, and other features. If some error is found, a pop-up window
appears, the debugger can stop, or a log is written to disk.
Delivered for 16- and 32-bit applications.
[DOWNLOAD##download##]
