IBM VisualAge C++ 4.0 Workframe: Difference between revisions
Appearance
mNo edit summary |
mNo edit summary |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
A fully integrated developer's workframe, with [[IBM VisualAge C++ 4.0 Compiler and Linker|compiler]], make and build tools, [[VAC_4.0_Debugger|debugger]] and class browser etc. directly built in. Unlike with version 3.0, the workframe is not integrated into the WPS any more, but it comes as an OS/2 and a Windows NT version. "Project files" are in a special ASCII format, replacing the VAC 3.0 "project" objects as well as the make files. This is a disadvantage if you want to port large projects from any make file based system to this workframe. The advantage is that projects are now portable from one system to the other. | |||
A fully integrated developer's workframe, with [[ | |||
== | ==See also== | ||
* [[ | * [[IBM VisualAge C++ Professional 4.0]] | ||
[[Category:Integrated Development Environment]] | |||
[[Category: |
Latest revision as of 20:23, 2 December 2019
A fully integrated developer's workframe, with compiler, make and build tools, debugger and class browser etc. directly built in. Unlike with version 3.0, the workframe is not integrated into the WPS any more, but it comes as an OS/2 and a Windows NT version. "Project files" are in a special ASCII format, replacing the VAC 3.0 "project" objects as well as the make files. This is a disadvantage if you want to port large projects from any make file based system to this workframe. The advantage is that projects are now portable from one system to the other.