readme.txt

borland c++ 4.0 用于学习ucos的

                   Welcome to Borland C++ 4.0
                   --------------------------

  This README file contains important information about Borland C++.
  For the latest information about Borland C++ and its accompanying
  programs and manuals, read this entire file.

-----------------
TABLE OF CONTENTS
-----------------
1.  How to Get Help
2.  Installation
3.  Features
     -Compiler
     -Linker
     -IDE
     -Turbo Debugger
     -Resource Workshop
     -ObjectWindows Library (OWL)
     -VBX Support
     -Documentation
4.  Important Information
     -General
     -New Tools
     -Running from a Windows 3.1 DOS Prompt
     -C/C++ Language Changes
     -Developing for NT
     -Libraries and Startup Code
     -New Compiler and Linker Switches
     -Converting Your Borland C++ 3.1 Windows Code to Borland C++ 4.0
     -Class Libraries
     -Casting Macros
     -IDE/Integrated Debugging
     -Floating Point Formats
     -Turbo Debugger for Windows
     -Using Tools with NTFS

------------------
1. HOW TO GET HELP
------------------

  If you have any problems, please read this file, the
  HELPME!.DOC and other files in your DOC subdirectory, and
  check the on-line help and the Borland C++ manuals first.
  If you still have a question and need assistance, help is
  available from the following sources:

  1. For instant on-line access to the Borland forums with
     their libraries of technical information and answers
     to common questions, type

        GO BCPPDOS     - for questions pertaining to DOS

         or

        GO BCPPWIN     - for questions pertaining to Windows

     If you are not a member of CompuServe, see the enclosed
     special offer, and write for full details on how to receive
     a free IntroPak containing a $15 credit toward your first
     month's on-line charges.

  2. Borland offers a wide variety of Technical Support plans
     providing a range of assistance from installation and general
     usage of Borland C++ to language syntax, programming, and
     debugging help. For information about these support programs,
     call 1-800-523-7070.

  3. Borland's TECHFAX service. Call [phone] for a FAX
      catalog of technical document entries.

  4. Borland DLBBS. Dial [phone] (up to 9600 baud, 8-N-1)
      for a host of free technical documents and example programs.

  5. For immediate assistance with everything from configuring Borland C++
      to programming or debugging, call our C++ Programmer's
      Advisor Lines ($2/minute, first minute free):
            * Windows / Win32:	1-900-555-1002  or 1-800-782-5558 (MC/Visa)
            * DOS :		1-900-555-1004  or 1-800-368-3366 (MC/Visa)

---------------
2. INSTALLATION
---------------
Important!
----------
Do not install Borland C++ 4.0 files over previously installed Borland
C++ directories. The files in this distribution will not work
with previously shipped tools and libraries.  This is particularly
true for configuration files from previous shipping
releases, like TDCONFIG.TDW and BCCONFIG.BCW.

Also, be especially careful when using object files and libraries
from Borland C++ 3.1 with binaries created with this release. There are 
several potential problems when linking with old objects or libraries. 
Exceptions won't work correctly (destructors won't get called) when a 
pre-BC4 stack frame is unwound due to an exception. Also, if a constructor 
or destructor compiled with a pre-BC4 compiler is involved in exception 
unwinding, trouble may occur. Another potential problem is when an RTTI class 
is shared with pre-BC4 code; some cases of that will be caught by the linker,
but others may fail mysteriously. Try using the -K2 switch to get pre-BC4 code
to link. Note: these problems are C++ specific. C objects between versions
should be more readily compatible.

Installing Borland C++ 4.0 on your hard disk:
--------------------------------------
Installing from floppy disks:
	1. Select File|Run from Windows 3.1, Windows for Workgroups 3.1x,
	   or Windows NT.
	2. Enter A:INSTALL (or B:INSTALL) on the input line.
	3. Under "Installation Options", you have the option of not
	   installing Win32s, which should be turned off if you are 
	   installing under Windows NT.
          (NOTE that BCW does not run under NT, so if you are only using
          NT, you may wish to not install it.)
	4. Fill in directories as appropriate, and INSTALL will create
          appropriate Windows groups, install Win32s, and install the
	   new Borland C++ 4.0 software according to the directories you select.

Installing from the CDROM:
	1. Go to the CDROM, and change directories to INSTALL.
	2. Select File|Run from Windows 3.1, Windows for Workgroups 3.1x,
	   or Windows NT.
	3. Enter X:INSTALL on the input line (where X: is your CDROM drive).
	4. Under "Installation Options", you have the option of not
	   installing Win32s, which should be turned off if you are
	   installing under Windows NT.
	5. Fill in directories as appropriate, and INSTALL will create
	   appropriate Windows groups, install Win32s, and install the
	   new Borland C++ 4.0 software according to the directories you select.

To use the built-in transfer tools and Help, make sure their location is
in your path (the \BIN directory for Borland C++ 4.0).

After installing, make sure your path is set correctly, and restart 
Windows before using Borland C++ 4.0.

NOTE: If you want to install the Win32s debug kernel, use the
SWITCH.BAT file provided with the Microsoft Win32s tools, found on the
NT SDK CD-ROM distribution.  This will ensure that the proper files
are copied to the appropriate places.  Not copying the files correctly 
will result in obscure load errors. 

Configuring Borland Pascal and Borland C++
------------------------------------------
The install program for Borland C++ 4.0 will configure your system to
allow the use of Borland C++ 4.0 and Borland Pascal 7.0 on the same
machine.  As long as you have installed Borland Pascal prior to
(rather than after) installing Borland C++ there are very few
guidelines you must follow:

- The two Windows hosted IDEs may not be run simultaneously.

- Each must use their respective copies of tools and utilities that
  depend on debug information, most notably Turbo Debugger for Windows
  (TDW).  You may find it useful to rename the Borland Pascal version
  of TDW.EXE to something like BPTDW.EXE to avoid confusing filenames
  in your path.

- Both versions of TDW may not be run simultaneously.

- Make sure that old copies of TDW.INI are removed from your system. 
  (Running the utility TDWINI.EXE will make sure that this takes
  place.)

That's all there is to it!  To reduce disk space requirements, you
may wish to remove duplicate versions of utilities that do not
require debug information, such as WinSight and Resource Workshop. 
In these cases, you will want to use the versions that came with
Borland C++ 4.0 so that you will have the latest features.

If you wish to use TDWGUI.DLL with TDW version 3.1 you need to
manually add UseTimer=Yes to the VideoOptions section of TDW.INI. 
Note that this option should not be set when using TDW version 4.0. 
This means that you would need to hand change your TDW.INI file each
time you switched between versions of TDW.  For this reason, we
recommend the non-windowed video DLLs (such as SVGA.DLL) for
customers who debug both BP and BC applications.

If you are installing Borland Pascal 7.0 AFTER Borland C++ 4.0 has
been installed, you will have to manually change the system settings
that allow these products to coexist:

In your system.ini file, check your [386Enh] section for multiple
entries for the device TDDEBUG.386.  Remove duplicate entries of
TDDEBUG.386 so that only the version from Borland C++ is loaded.  On
disk, you may also want to rename or remove the BP7 versions of
TDDEBUG.386 and TDWIN.DLL to avoid their accidental loading.  You
must restart Windows after making changes to system.ini.

Win32s and minimum swap file size
---------------------------------
Borland recommends that you have a minimum of 12 MB of memory available to
run Win32s applications.  For example, if your machine has 8 MB of memory
available to Windows, you should configure your "Virtual Memory" (swapfile)
to at least 4 MB.  This will reduce the risk of out-of-memory errors 
occuring in Win32s.

NT console applications and Win32s
----------------------------------
There is no Win32s console, so attempting to run a Win32 console
application without NT loaded will result in an error.

Changes to SYSTEM.INI file
--------------------------
The install program makes these changes to the SYSTEM.INI file:

  1) Adds "device=c:\bc4\bin\windpmi.386" to support our 32-bit tools.
  2) Adds "device=c:\bc4\bin\tddebug.386" to support our debugger.


Configuring the Windows NT command prompt
-----------------------------------------
To run 16-bit protected-mode programs (bcc, tlink) under an NT command prompt
you need to add the following line to CONFIG.NT:

  ntcmdprompt

Under the default NT command-line prompt, DOS COMMAND.COM is run after
returning from a TSR (such as RTM.EXE which bcc and tlink load). Adding the 
above line will cause the original NT CMD.EXE to be run.


Outdated versions of Win32s
---------------------------
If you are running an outdated version of Win32s, the INSTALL program will
instruct you to remove it before installation.  To remove an old
version of Win32s perform the following steps:

  1. Change directory to the WINDOWS directory on your hard drive.  This
     is most likely C:\WINDOWS.

  2. Edit the SYSTEM.INI file and remove the line in the [386Enh]
     section that reads:

       device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386

     (The actual path in the above line may be different to reflect your
      configuration.)

  3. Change directory to the SYSTEM subdirectory.

  4. Remove the following files:

       W32SYS.DLL
       WIN32S.INI
       WIN32S16.DLL

  5. Change directory to the WIN32S subdirectory.

  6. Remove all files here.

  7. Change directory back to SYSTEM and remove the WIN32S subdirectory.

You will now be ready to run the INSTALL program.  Be sure to select
<Install Win32s> in the INSTALL program so that the newer version of Win32s
will be installed on your system.


-----------
3. FEATURES
-----------

Compiler:
---------
  - Support for writing 16 and 32-bit Windows applications that target
    Windows 3.1, Win32s and Windows NT, and 16-bit DOS applications.
  - Pentium support.
  - Support for ANSI C++ exception handling, structured exception handling
    under C, and mixed C/C++ exception handling. All exception handling
    constructs are available for both 16- and 32-bit.
  - Additional optimizations and faster compile time.
  - Support for ANSI C++ operator new[] and operator delete[].
  - Runtime Library support for the ANSI C++ string class.
  - Support for ANSI C++ runtime type identification (RTTI).
  - Support for ANSI C++ new style casts dynamic_cast, static_cast, const_cast,
    and  reinterpret_cast.
  - Support for three character types as provided in ANSI C++.

Linker (16-bit and 32-bit):
---------------------------
  - Now handles binding of resources; no need for a separate RC or
    RLINK step.
  - Linker debug capacity expanded.

IDE
---
  - 16-bit DOS and Windows plus 32-bit Windows targeting from a single IDE.
  - Integrated GUI debugging for 16-bit Windows applications.
  - Includes both 16- and 32-bit tools (compiler, linker, resource 
    compiler, resource binder, and library manager)  
  - A new project manager that supports multiple targets, drag-and-drop,
    and Style Sheets for associating options. 
  - AppExpert, which simplifies the process of creating
    ObjectWindows applications through code generation.
  - ClassExpert, which simplifies adding and managing classes in
    your AppExpert application.
  - Transfers, Settings Notebook, SpeedMenus, and a configurable SpeedBar.
  - Expanded editor support, including column blocking and window 
    splitting.  TEMC now called KEYMAPR.
  
Turbo Debugger:
---------------
  - Turbo Debugger (TD32) for Win32s and Windows NT.
  - Support for OS exception handling.
  - Support C/C++ exception handling.
  - Windows NT thread support.
  - Video DLL to run TDW in a window.
  - Remote debugging with TDW.
  - Session state saving.
  - Process attach for Windows NT.
  - Turbo Debugger Video Configuration Utility (TDWINI.EXE). 
  - Built in large model for greater capacity.

Resource Workshop:
------------------
  - Support for Win32s, Win32.
  - Resource preview
  - DialogExpert
  - Auto ID numbering
  - Auto mapping of accelerators and help hints to menu items
  - Support for VBX controls
  - SpeedMenus
  - Dialog editor property inspector
  - Integrated with ClassExpert and IDE project manager

ObjectWindows Library (OWL)
---------------------------
  - Complete coverage of Windows API, including GDI
  - Single source for Win 3.1, Win 32s, and NT
  - Built in exception handling using standard C++ exceptions for robust error
    handling
  - Built-in type safety using standard C++ templates
  - Toolbars, status lines, and print preview
  - Flexible Document/View architecture
  - Supports VBX 1.0 controls in a dialog or window
  - Layout Windows
  - Mix-in architecture
  - Support for 3d controls
  - Support for BWCC controls
  - Gadgets and Widgets
  - Multi threading support
  - Printing and print previewing support

VBX Support
-----------
Borland's visual tools, such as Resource Workshop, provide support of VBX 1.0
controls via a DLL called BIVBX10.DLL. You can freely distrubute this DLL
with programs you create that use VBX controls.

BIVBX10.DLL has been tested with a large number of VBX controls written to the
Microsoft Visual Basic 1.0 CDK specification. If you have a problem with a
specific control, make sure that it does not require VB 2.0 or VB 3.0 CDK
functionality. VBX 2.0 and 3.0 controls will usually display a message saying
that they require VB 2.0 or 3.0 support. In some cases, though, the control may
appear to work but exhibit instability. Please contact the control vendor and
explain the problem. They may have an updated control or may be able to contact
Borland to find a solution.

Documentation:
--------------
This distribution includes printed and online documentation
to help you understand and use the new features of Borland C++ 4.0, as well
as online Help.  

For C++ Language and Programming information:
	See the Library Reference, the
	Programmer's Guide, and the DOS Reference.
	See also the online Help.

For information on using MAKE, TLINK, and resource tools: