|
- Visual Workbench replaces the Programmer's Workbench (PWB)
- QuickHelp utility system (QH.EXE) and QuickHelp files no longer available
-
New 32-bit Tools:
While the IDE (MSVC.EXE) was a 16-bit windows application (NE file format), the tools below
became 32-bit MS-DOS extended programs requiring a 386 processor running in protected mode
and the DOS Extender, DOSXNT.EXE. Additionally to be able to run these on Windows 3.1, the
DOSXNT.386 driver was required.
- BSCMAKE.EXE
- CL.EXE
- CVPACK.EXE
- LINK.EXE
- NMAKE.EXE
-
The following tools were depreciated:
- BSCMAKEV.EXE
- EXP.EXE
- HELPMAKE.EXE
- ILINK.EXE
- PWBRMAKE.EXE
- QH.EXE
- RM.EXE
- UNDEL.EXE
- WX.EXE
- WXSRVR.EXE
-
[COMPILER]
- An automatic precompiled header facility (/YX) that simplifies the creation and use of
precompiled header files.
- A programming database (PDB) that speeds linking during the debugging phase of program
development. The compiler creates a .PDB file when you use /Zi to generate complete
debugging information. The new /Z7 option, which generates Microsoft C/C++ version 7.0
debugging information, provides the old functionality of /Zi.
- The ability to generate more efficient code, using the /G3 option, for programs that target 16-bit
operating environments running on computers with 80386, or greater, microprocessors.
- The ability to specify string pooling, using the /Gf option.
- The default use of the /Gx option. With the compact, large, or huge memory models, the /Gx
option allocates memory in the default near data segment for all initialized and uninitialized data
and data marked as extern if the data items are smaller than or equal in size to the threshold
value set by the /Gt option. The new /Gx- option turns off the default use of /Gx.
- The ability to compile for very small or very fast code, using /O1 or /O2, respectively.
- The ability to control inlining by function size, using /OVn.
- The ability to suppress or enable hidden vtordisp class members, using /vdn.
- The ability to use pointers to member functions, using five new options (/vmb, /vmg, /vms,
/vmm, and /vmv) and a new pragma (pointers_to_members).
- The ability to use extended memory. CL is MS-DOS extended and requires certain services in
order to run with MS-DOS or Microsoft Windows. CL cannot run with real-mode MS-DOS.
-
[LINKER]
- The linker provided with Microsoft Visual C++ is MS-DOS extended and requires certain
services in order to run with MS-DOS or Windows. LINK cannot run with real-mode
MS-DOS. The /r option to run with real-mode MS-DOS has been removed.
- LINK looks for a .PDB file if an .OBJ file was compiled with Visual C++ using /Zi.
Programming database (.PDB) files store debugging information. If /CO is specified, LINK
uses .PDB files to create an executable file that can be debugged.
- LINK now recognizes p-code and calls the Make P-Code Utility (MPC) automatically. You do
not need to specify the /PCODE option.
-
Two changes in LINK 5.50 concern files that LINK requires when linking for debugging using
the /CO option. LINK no longer looks for CVPACK.EXE when linking a program for debugging.
If you created an object file by specifying the /Zi option to the Microsoft Visual C++ compiler, the
program database (.PDB) file for that object file must be available when you link.
LINK versions 5.30 and later support two types of overlaid MS-DOS programs, dynamic (using
MOVE.LIB) and static. Previous versions of LINK supported only static overlays. This chapter
describes several LINK features for dynamic overlays. It does not describe static overlays, which
may not be supported in the future.
The program ILINK.EXE is not provided with Microsoft Visual C++. Check any existing
makefiles and batch files for commands to call ILINK.
The following options are new or changed in LINK versions 5.30 and later:
-
/CO[DEVIEW]
When using /CO to link objects that were compiled using /Zi in Microsoft Visual C++, the
.PDB files must be available.
-
/DOSS[EG]
The minimum unique abbreviation for the /DOSSEG option has changed from /DO to /DOSS.
-
/DY[NAMIC][:number]
The new /DYNAMIC option lets you change the limit of interoverlay calls in an overlaid
MS-DOS program.
-
/INC[REMENTAL]
The /INCR option is no longer supported.
-
/I[NFORMATION]
The /INFO option gives more detailed output. One new use is to get the number of interoverlay
calls needed to specify with the /DYNAMIC option.
-
/M[AP][:maptype]
The /MAP option has been enhanced. You can get more or less detail in the map file by
specifying an optional qualifier.
-
/NOPACKC[ODE]
The minimum unique abbreviation for /NOPACKC has changed from /NOP to /NOPACKC
to distinguish it from the new /NOPACKF option.
-
/NOPACKF[UNCTIONS]
The new /NOPACKF option keeps unreferenced packaged functions.
-
/OL[DOVERLAY]
The new /OLDOVERLAY option links an overlaid MS-DOS program using the Static Overlay
Manager instead of the MOVE library. This option may not be supported in future versions of
LINK.
-
/ON[ERROR]:N[OEXE]
The new /ONERROR:NOEXE option prevents LINK from creating the program output if an
error occurs.
-
/OV[ERLAYINTERRUPT]
The minimum unique abbreviation for this option has changed from /O to /OV, to distinguish it
from the new /OLDOVERLAY option.
-
/PACKF[UNCTIONS]
The new /PACKF option removes unreferenced packaged functions.
-
/PADC[ODE]
The /PADC option is no longer supported.
-
/PADD[ATA]
The /PADD option is no longer supported.
-
/PC[ODE][:NOMPC]
The new /PCODE option specifies whether the Make P-Code Utility (MPC) is called after
linking.
-
/PM[TYPE]
The default for the /PM option has changed from NOVIO to PM.
-
/r
The /r option was new in LINK versions 5.3x and is removed in version 5.50.
-
A new overlay manager, the Microsoft Overlaid Virtual Environment (MOVE), replaces the
Microsoft Static Overlay Manager.
-
You can now use a module-definition file when you link an MS-DOS application. LINK creates an
MS-DOS executable file instead of a segmented executable file if the .DEF file contains any of the
following:
- An EXETYPE statement that specifies the type DOS
- A SEGMENTS statement that specifies an overlay number
- A FUNCTIONS statement that specifies an overlay number
Other conditions also determine the type of executable file that LINK creates.
The only valid statements in a .DEF file for an MS-DOS program are
EXETYPE, SEGMENTS, FUNCTIONS, and INCLUDE. All other statements are ignored.
-
New statements and changes to existing statements described in this chapter are:
- The NAME statement's default apptype is now WINDOWAPI (formerly NOTWINDOWCOMPAT).
- The EXETYPE statement's default is now WINDOWS.
- EXETYPE WINDOWS now assumes PROTMODE by default.
- The EXETYPE statement has a new type argument, DOS.
- The new SECTIONS and OBJECTS keywords are synonyms for the SEGMENTS statement.
- The SEGMENTS statement accepts a new argument, OVL:number. This argument specifies
the overlay in which the segment belongs in an overlaid MS-DOS program.
- The new FUNCTIONS statement specifies the order in which functions appear in the
executable file. It can also assign functions to a specific segment. In an overlaid MS-DOS
program, FUNCTIONS can specify the overlay in which functions belong.
- The new INCLUDE statement inserts module statements from a separate text file.
-
[SOURCE PROFILER]
The Source Profiler version 1.3 provides features including:
- Support for language features, such as objects and p-code.
- Support for CodeView version 3.x and later symbolic debugging information.
- The ability to profile reloaded dynamically loaded dynamic-link libraries in Windows.
- The ability to specify additional directories for the PLIST utility to search for source code
information.
|
| |
|
|
|