很老的Watcom编译器

WATCOM C/C++ Version 11.0 - README ---------------------------------- Welcome to WATCOM C/C++ version 11.0. This README provides helpful hints found during testing as well as updated information that was not available at the time the documentation was produced. Changes in 11.0 that may Require Recompilation: ----------------------------------------------- clock() The clock function accuracy has changed from 100 ticks per second to 1000 ticks per second (i.e., CLOCKS_PER_SEC has changed). Source code that uses the clock function and CLOCKS_PER_SEC in its calculations must be recompiled before linking the application with new libraries. Major Differences from Version 10.6: ------------------------------------ The following sections summarize the major differences from the previous release of Watcom C/C++. In general, we have improved Microsoft compatibility in our compilers (more warnings instead of errors, support for MS extensions, etc.) and tools. Some of the Win32 and 32-bit OS/2 versions of our tools are now available in DLL form. EXE DLL Description ------ ------- ----------------------- wcc wccd 16-bit x86 C compiler wcc386 wccd386 32-bit x86 C compiler wpp wppdi86 16-bit x86 C++ compiler wpp386 wppd386 32-bit x86 C++ compiler wlink wlink Watcom Linker wlib wlibd Watcom Library Manager This provides better performance when using the Integrated Development Environment or Watcom Make. See the description of the !loaddll preprocessing directive in Watcom Make for more information. Changes to the C++ Compiler for 11.0 ------------------------------------ We have added support for namespaces and RTTI (Run-Time Type Identification). We have improved (faster) pre-compiled header support. We have added "long long" (64-bit integer) support in the form of a new __int64 type. Changes to the C Compiler for 11.0 ---------------------------------- We have improved (faster) pre-compiled header support. We have added "long long" (64-bit integer) support in the form of a new __int64 type. Changes to the Code Generator for 11.0 -------------------------------------- A new optimization, "branch prediction", has been added. This optimization is enabled by the "ob" or "ox" compiler options. The code generator tries to increase the density of cache use by predicting branches based upon heuristics (this optimization is especially important for Intel's Pentium Pro). We have added Multi-media Extensions (MMX) support to the in-line assemblers. We have added "long long" (64-bit integer) support in the form of a new __int64 type. Changes to the Compiler Tools for 11.0 -------------------------------------- The Watcom Linker supports incremental linking. The Watcom Library Manager (WLIB) can now understand COFF and ELF format object files, as well as OMF et al. The Watcom Library Manager can now read/write AR-format (Microsoft compatible), Multilib (used by IBM for PowerPC version of OS/2), or old-style OMF libraries. The default output format is AR-format and this can be changed by switches. The Watcom Library Manager can output various format import libraries. We have added Multi-media Extensions (MMX) support to the Watcom Assembler (WASM). A new version of the Watcom Disassembler (WDIS) is included. It can process ELF, COFF or OMF object files and ELF, COFF or PE format (Win32) executables. The old disassembler (WDISASM) has been retired and is not included in the package. We have added new tool front-ends that emulate Microsoft tools. These are: nmake cl link lib rc cvtres mapsym These programs take the usual Microsoft arguments and translate them, where possible, into equivalent Watcom arguments and spawn the equivalent Watcom tools. Watcom Make now processes Microsoft format makefiles when the "ms" option is used. Changes to the C/C++ Libraries for 11.0 --------------------------------------- We have added multi-byte and wide character (including UNICODE) support to the libraries. We include run-time DLLs for the C, Math and C++ Libraries. We have added Multi-media Extensions (MMX) support to the libraries. The following new functions were added to the library... mb functions The clock function accuracy has changed from 100 ticks per second to 1000 ticks per second (i.e., CLOCKS_PER_SEC has changed). Changes to the DOS Graphics Library for 11.0 -------------------------------------------- The graphics library now performs the VESA test before testing for vendor specific graphics cards. This fix is intended to broaden the number of graphics cards that are supported. Changes in Microsoft Foundation Classes Support for 11.0 -------------------------------------------------------- Version 4.1 of the 32-bit MFC is included in the package. Version 2.52b of the 16-bit MFC is included in the package. Changes in Microsoft Win32 SDK Support for 11.0 ----------------------------------------------- We include the full Win32 SDK (including all samples). The Win32 SDK is supported for Windows 95 and Windows NT platforms. Microsoft DirectX SDK Now Included in 11.0 ------------------------------------------ We have licensed the DirectX SDK from Microsoft for those customers who develop games. Changes in Blue Sky's Visual Programmer for 11.0 ------------------------------------------------ A new 32-bit version of Visual Programmer is included in the package. This version runs on 32-bit Windows 95 and NT. It also runs on 16-bit Windows when Win32s support is installed. The 16-bit version of Visual Programmer is no longer included in the package. You can generate 16-bit applications with it, but you must be careful to avoid using Win95 controls. This new version fixes all known bugs in the previous version. For details on what was new in versions 10.6 and earlier, see the GETTING STARTED helpfile. Other notes: Note: %DstDir% represents the directory in which WATCOM C/C++ was installed. %WinSysDir% represents your Windows 3.x system directory. 1. When debugging a 32-bit Phar Lap, TNT or DOS/4GW application, make sure that "run386.exe", "tnt.exe", or "dos4gw.exe" respectively, are in your path. Failure to do so, may cause your computer to hang. 2. When using the GUI debugger to debug Windows 3.x applications, certain Windows applications may cause the debugger to behave in an unpredictable way. Typically, this occurs when debugging certain messages in window callback functions. For example, hitting a breakpoint in a window function that is processing a WM_INITDIALOG message will crash the system. If this happens, the character-mode version of the debugger should be used. 3. When debugging the Windows 3.x MFC 2.52 samples contained in "%DstDir%\src\mfc\v252" enter the following in the source path to see the MFC source in the debugger source window. %DstDir%\src\mfc\v252\*.cpp Similarly, when debugging the Windows NT MFC 4.1 samples contained in "%DstDir%\src\mfc\v41" enter the following in the source path to see the MFC source in the debugger source window. %DstDir%\src\mfc\v41\*.cpp The source path can be changed by selecting "Source Path" in the "File" menu. 4. In order to use CodeWright with our IDE, you will need to change the "cwright.ini" file. This file contains the following line. ;LibPreload=cwdde.dll Uncomment this line by removing the ';' character. This is required to enable communication between the IDE and CodeWright when "weditcw.dll" is selected as the editor interface DLL from the IDE. 5. If you choose to not install help files onto your hard disk, you will not be able to get help on the C library or MFC library