文件列表:

BORLANDC\BGI\ATT.BGI (6332, 1992-06-10)
BORLANDC\BGI\BGIDEMO.C (40382, 1992-06-10)
BORLANDC\BGI\BGIOBJ.EXE (12208, 1992-06-10)
BORLANDC\BGI\BOLD.CHR (14670, 1992-06-10)
BORLANDC\BGI\CGA.BGI (6332, 1992-06-10)
BORLANDC\BGI\EGAVGA.BGI (5554, 1992-06-10)
BORLANDC\BGI\EGAVGA.OBJ (5658, 2005-04-25)
BORLANDC\BGI\EURO.CHR (8439, 1992-06-10)
BORLANDC\BGI\GOTH.CHR (18063, 1992-06-10)
BORLANDC\BGI\HERC.BGI (6204, 1992-06-10)
BORLANDC\BGI\IBM8514.BGI (6665, 1992-06-10)
BORLANDC\BGI\LCOM.CHR (12083, 1992-06-10)
BORLANDC\BGI\LITT.CHR (5131, 1992-06-10)
BORLANDC\BGI\PC3270.BGI (6012, 1992-06-10)
BORLANDC\BGI\SANS.CHR (13596, 1992-06-10)
BORLANDC\BGI\SCRI.CHR (10987, 1992-06-10)
BORLANDC\BGI\SIMP.CHR (8437, 1992-06-10)
BORLANDC\BGI\TRIP.CHR (16677, 1992-06-10)
BORLANDC\BGI\TSCR.CHR (17355, 1992-06-10)
BORLANDC\BIN\ATI.DLL (20992, 1992-06-10)
BORLANDC\BIN\BC.EXE (1410992, 1992-06-10)
BORLANDC\BIN\BC.ICO (766, 1992-06-10)
BORLANDC\BIN\BC.PIF (545, 1992-06-10)
BORLANDC\BIN\BC30RTL.DLL (143802, 1992-06-10)
BORLANDC\BIN\BCC.EXE (672150, 1992-06-10)
BORLANDC\BIN\BCW.EXE (1366544, 1992-06-10)
BORLANDC\BIN\BIDS31.DLL (74148, 1992-06-10)
BORLANDC\BIN\BORTE.FON (12276, 1992-06-10)
BORLANDC\BIN\BRC.EXE (27520, 1992-06-10)
BORLANDC\BIN\BRCC.EXE (306672, 1992-06-10)
BORLANDC\BIN\BRCWIN.DLL (296848, 1992-06-10)
BORLANDC\BIN\BUILDSYM.EXE (13750, 1992-06-10)
BORLANDC\BIN\BUILTINS.MAK (353, 1992-06-10)
BORLANDC\BIN\COMPRESS.EXE (15259, 1992-06-10)
BORLANDC\BIN\CPP.EXE (131625, 1992-06-10)
BORLANDC\BIN\DFA.EXE (56486, 1992-06-10)
BORLANDC\BIN\DPMI16BI.OVL (60672, 1992-06-10)
BORLANDC\BIN\DPMIINST.EXE (35524, 1992-06-10)
BORLANDC\BIN\DPMILOAD.EXE (22212, 1992-06-10)
BORLANDC\BIN\DPMIMEM.DLL (24932, 1992-06-10)
... ...

Welcome to Borland C++ & Application Frameworks 3.1 --------------------------------------------------- This README file contains important information about Borland C++. For the latest information about Borland C++ and its accompanying programs and manuals, read this file in its entirety. TABLE OF CONTENTS ----------------- 1. How to Get Help 2. Installation 3. Features 4. Important Information 5. Testing Your Expanded Memory 6. Corrections to the Documents 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 the Borland C++ manuals first. If you still have a question and need assistance, help is available from the following sources: 1. Type GO BCPPDOS - for questions pertaining to DOS or GO BCPPWIN - for questions pertaining to Windows on the CompuServe bulletin board system for instant access to the Borland forums with their libraries of technical information and answers to common questions. 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. Check with your local software dealer or users' group. 3. Borland's TECHFAX service. Call (800) 822-4269 for a FAX catalog of entries. 4. If you have an urgent problem that cannot wait and you have sent in the license agreement that came with the package, you may call the Borland Technical Support Department at (408) 461-9133. Please have the following information ready before calling: a. Product name and serial number on your original distribution disk. Please have your serial number ready or we will be unable to process your call. b. Product version number. The version number for Borland C++ can be displayed by pressing Alt-H/A in the IDE. c. Computer brand, model, and the brands and model numbers of any additional hardware. d. Operating system and version number. (The version number can be determined by typing VER at the DOS prompt.) e. Contents of your AUTOEXEC.BAT file. f. Contents of your CONFIG.SYS file. 2. INSTALLATION ---------------- You MUST use the INSTALL program to install Borland C++. The files on the distribution disks are all archived and have to be properly assembled. You cannot do this by hand! Installing to the same directory structure as a previous version without erasing the directories is not recommended; you may encounter problems due to old header files, libraries, memory managers, or configuration files. To start the installation, change your current drive to the one that has the install program on it and type INSTALL. You will be given instructions in a box at the bottom of the screen for each prompt. For example, if you will be installing from drive A:, type: A: INSTALL - This INSTALL handles the installation of both the compiler and debugger and tools in one operation, and allows several new configuration options. - Note: The list of files is contained in a separate file called FILELIST.DOC, which will appear in the target directory you specify during installation. - After installation, make sure you insert \BORLANDC\BIN - or whatever you selected as your BIN directory - into your DOS path so the DLL and executable files can be found. - If you have previously installed Resource Workshop, make sure that you remove the directory of that version from your path. The version included on these disks supercedes previous versions. - If you use a Windows command shell other than Program Manager, you may not get a Borland C++ group installed for Windows. If you don't, use File|Run in Program Manager to run the following command: GROUPS GROUPS.B$$ You will then have a new group for Borland C++. - After your initial installation, you can run INSTALL again to add elements you omitted the first time. Select only the things you want to add in the INSTALL options screen. Because some things you may want to save could be overwritten, review the following items to make sure you don't lose important information: 1. Selecting CMD (the Command-line compiler) causes an overwrite of any existing TURBOC.CFG & TLINK.CFG file with path information provided in that INSTALL session. Any switches that you have added will not be preserved. 2. By selecting any one of the following, the help file paths and choices for THELP.CFG will reflect the current session's installation choices: a. CMD - command-line compiler b. IDE - integrated environment c. TD - Turbo Debugger d. TASM - Turbo Assembler e. TV - Turbo Vision f. OWL - ObjectWindows library 3. If you have made any alterations to headers or startup files they will be overwritten if any library models are selected. 4. Selecting the Create BorlandC++ Group option will add a group to the desktop and insert the appropriate icons into that group if this is a first time installation. If this is a re-installation this option will insert the appropriate icons into the existing group. In general, any selection you make of something installed earlier will cause an overwrite of the earlier version without prompting. An attempt to install to a network directory for which you don't have delete rights will fail with the message "Invalid directory." Make sure delete rights are secured before attempting an installation to a network. You should read the rest of this README file to get further information about this release before you do the installation. See also the files in the DOC subdirectory after installation for general information not included in the manuals. 3. NEW FEATURES ---------------- - Borland C++ for Windows: A Windows-hosted IDE which produces Optimized code. The same Optimization options available in BC.EXE are in BCW.EXE. - Color syntax highlighting: All IDEs now highlight your source according to syntax. See the choices under Options|Environment| Colors|Edit Window in the DOS IDE and Options|Environment| Highlight in the Windows IDEs. This option is enabled by Options|Environment|Editor|Syntax Highlighting. - 386 code generation: An option has been added to produce 386 instructions in the generated code. Use -3 at the command line, or Options|Compiler|Advanced Code Generation|80386 in the IDEs. - The Object Data calling convention for improved efficiency of C++ code. See the User's Guide chapter, "The Command-line Compiler", under the option -po for more information. This option is also available under Options|Compiler|Optimizations|Object data calling in the IDE. - Windows 3.1 support: All executables and DLLs have been modified appropriately for compatibility with Version 3.1 of Windows. The ObjectWindows Library header files have been modified for compatibility with the new Windows header files as well. NOTE CONCERNING USE OF MICROSOFT WINDOWS 3.1 REDISTRIBUTABLES FOR APPLICATIONS RUNNING ON MICROSOFT WINDOWS 3.0 This Borland language product contains everything you need to develop applications to run on the most recent version of Microsoft Windows, version 3.1. In some cases, you may need to copy and include in your application one or more Microsoft "redistributable" files from a copy of version 3.1 so that your application will also run on version 3.0. Microsoft informs us that you may copy the redistributable files from from Microsoft Windows 3.1 for this purpose. If you do so, you must comply with the conditions stated in the Borland No-Nonsense License Statement included in this package as if the redistributable files you copy were a part of this Borland language product. Microsoft's redistributable files in Windows 3.1 are: winhelp.exe, winhelp.hlp, commdlg.dll, ddeml.dll, toolhelp.dll, vtd.386, olecli.dll, olesvr.dll, ver.dll, lzexpand.dll, expand.exe, regload.exe, stress.dll, dib.drv, markmidi.exe, penwin.dll, and shell.dll. If you do not find any of these files in the BIN directory, they are also included in the Windows retail distribution, and installed in your Windows directories. - WinSpector, a postmortem Windows debugging tool that traps general protection faults and provides information on where the fault occurred and the state of the machine at the time. - You can now increase the number of files that can be open at one time in a DOS program by a simple modification of the runtime library. First, modify _NFILE.H in your INCLUDE directory by changing the #define for _NFILE_: #define _NFILE_ n where n is the number of files you want to open. Make sure the FILES statement in your CONFIG.SYS file specifies at least this number. Then compile the two files FILES.C and FILES2.C in the LIB directory: BCC -c -m files.c files2.c where is the memory model you're using. Then link them directly with the program which opens the files, for instance: BCC myfile.c files.obj files2.obj If you want the change to apply to all modules, add FILES.OBJ and FILES2.OBJ created above to the libraries you use; from the LIB directory, type: TLIB c +-files.obj +-files2.obj where matches what you used for the BCC command above. DPMI ---- BC.EXE, BCC.EXE, MAKE.EXE, and TLINK.EXE are now hosted under DPMI. These files replace both the files with the same name in Borland C++ 2.0 and the BCX.EXE, BCCX.EXE, and TLINKX.EXE files in the same product. There is no longer a TKERNEL.EXE file. Important! ---------- You must have at least 1Mb of extended memory to run these programs. If you encounter a "machine not in database" message while attempting to run the compiler, run the DPMIINST program to add your machine configuration to the DPMI server database. This version includes a resident DPMI host program, DPMIRES.EXE, that allows you to preload the server before invoking BC, BCC, or any other DPMI-hosted executables. If you want to run such hosted EXEs in a Windows Standard Mode DOS window, you should run DPMIRES.EXE before loading Windows. To do this, enter the following commands at DOS: set DPMIMEM=MAXMEM 2000 dpmires win /s If you want to limit the amount of extended memory used by the DPMI-hosted executables, an environment variable called DPMIMEM can be set to do so. For instance, the command set DPMIMEM=MAXMEM 2000 reserves about 2 Mb of memory for DPMIRES. The number after MAXMEM can be adjusted, but cannot be lower than 1000. DPMIRES should not be run before running Windows in Enhanced Mode. Windows requires its own DPMI services. The hosted executables cannot spawn each other when SHARE is loaded. For instance, if you run MAKE on a file which in turn calls MAKE again, you will get a sharing violation. In this specific case, you can call the real mode version, MAKER, within the given makefile, and a sharing violation won't occur. Note to OS/2 users: To run any DPMI-hosted executables, like BC, BCC, or TLINK, in a DOS Window, you need to enable DPMI for that window: - Click the right mouse button on a DOS window icon in Command Prompts - Select Open|Settings|Session|DOS Settings|DPMI_DOS_API and select ENABLED. Note to EMM386.SYS users: To run DPMI-hosted EXEs, under the EMM386 included with Windows 3.1, you need to apply a patch to our files as follows: - Go to the BIN directory - Type the following command: patch server.dif dpmi16bi.ovl You will now be able to run BC, BCC, etc. 4. IMPORTANT INFORMATION ------------------------- - There is now only one version of the DOS IDE, BC.EXE, and of the command-line compiler program, BCC.EXE. Because the BCX and BCCX files are no longer in Borland C++, you'll need to alter batch or make files that use those names. - Borland C++ only supports Protected Mode Windows target files. Make sure to use the /t option when using the Resource Compiler if you want to enforce Protected Mode usage. - When using Brief with THELP, make sure to use Brief's -p switch to ensure that the THELP window will be visible. - We recommend that you use the following mouse drivers with this product: Microsoft Mouse version 7.04 or later; Logitech Mouse version 5.01 or later; Genius Mouse version 9.06 or later. - If you use MAKE or the IDE's Project Make to invoke the Resource Compiler, the .RC files you wish to compile MUST be in the same directory as your project or makefile. This is because the Microsoft Resource Compiler does not properly handle relative path names, and returns a misleading error message that refers to an incorrectly spelled version of your .RC file. - If you get a "floating point formats not linked" message at runtime, put the following somewhere in your source files: extern void _floatconvert(); #pragma extref _floatconvert This will force inclusion of floating point formats, which may not be linked to reduce executable size. - Make sure that you use the -WE switch (Options|Compiler|Entry| Windows explicit functions exported in the IDE) when using the fastcall modifier. The same applies when using the fastcall compilation option (-pr on the command line, Options|Compiler|Entry|Register in the IDE.) Also see the first entry on using fastcall with main() in "COMPILER" below. - If the Windows 3.0 home directory precedes the Borland C++ BIN directory in your path, attempting to access Help will result in the message "This version of Help file not supported." To enable Help, either reorder your path or copy WINHELP.EXE to your Windows 3.0 directory. - This compiler uses more strict checking of C++ syntax and argument matching than previous versions. You can expect more warning and error messages based on the ANSI C++ version 3.0 standard. - If you receive a "bad object record" message from the linker when building OWL or container class library applications, you are probably using the Borland C++ version 3.0 class libraries and/or OWL libraries. Make sure your library path specifies version 3.1 libraries for those applications. COMPILER - When using fastcalls (-pr command line option) you are required to explicitly use the C calling convention, "cdecl", for main. For example: int cdecl main( ) In Borland C++ 3.0 the compiler did not correctly name main when fastcalls were used, with the result that you were not required to cdecl main (in all cases). This is a dangerous condition and the compiler now (correctly) names main, resulting in a linker error in Borland C++ 3.1 for those Borland C++ 3.0 compiled programs that didn't cdecl main. Please correct any "non-cdecl main" definitions, if compiled with fastcalls. - In Borland C++ 3.0 the compiler allowed conversions from "const void*" to "void *", contrary to ANSI; for Borland C++ 3.1 this is no longer allowed. In addition, several other conversions regarding const variables have also been restricted. If you are a user of the const keyword, expect that you may have conversions that were allowed to exist with Borland C++ 3.0 that will need to be changed in order to compile using Borland C++ 3.1. - In Borland C++ 3.0 the following syntax was allowed- class foo{ ... } // note that the semicolon is missing here f(){ ... } The new compiler now requires the semicolon to be added after the class declaration. The compiler would interpret the example above as an attempt to return a class declaration to f(). - A new implicit conversion rule is now enforced for constructors. From page 573 of The C++ Programming Language 2nd Edition: "When no constructor for class X accepts the given type, no attempt is made to find other constructors or conversion functions to convert the assigned value into a type acceptable to a constructor for class X." For example, class X { /* ... */ X(int); }; class Y { /* ... */ Y(X); }; Y a = 1; // illegal: Y(X(1)) not tried Note that this rule only applies to constructors with ONE parameter. - The inport/outport functions have been changed to accept an unsigned parameter instead of an int. The new prototypes are: unsigned inport(unsigned) unsigned char inportb(unsigned) void outport(unsigned, unsigned) void outportb(unsigned, unsigned char) - We have new resource compiler and linker components: BRCC is the Borland Resource Compiler. RLINK is the resource linker/binder. BRC.EXE calls BRCC.EXE and RLINK.EXE, and is an equivalent to Microsoft's Windows 3.1 RC. New features that may not be found in other products include: - Binding of multiple RES files is supported under RLINK. - Resource ID conflicts are detected and resolved during binding. For more information, see the file MANUAL.RW located in your \BORLANDC\DOC directory. - There is currently support in ObjectWindows for STRICT and non-STRICT versions of OWL programs for Borland C++ versions 3.0 and 3.1. Simply define the macros WIN30 or WIN31, and add a definition for STRICT if you need STRICT compliance. For more details see WIN31.DOC in the DOC directory and OWL31.DOC in the OWL\DOC directory. - The default extension for source files to the command-line compiler is .CPP; that is, if you enter BCC -c test the compiler will search for test.cpp, and give an error if a file of that name cannot be found. If you want to have the command-line compiler assume a .c extension and C language source, use the command-line option -P-c. For more information, see "The command-line compiler" in the User's Guide. - Note that the Generate COMDEFs choice under Options|Compiler|Code Generation and the -Fc command-line option are only supported in the C language. Linker errors will result if you attempt to use a communal variable in C++. ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：