home *** CD-ROM | disk | FTP | other *** search
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- Turbo C TOOLS/2.0
-
- Version 6.00
- March 31, 1989
-
-
- This document provides information on the installation and use of Turbo C
- TOOLS/2.0. It should be used as a supplement to the manual. Please read the
- Introduction and "Using Turbo C TOOLS" in the manual. Then read this file
- for information specific to your C compiler and to this version of Turbo C
- TOOLS.
-
- Copyright (C) Blaise Computing Inc. 1989. All rights reserved.
-
- The PACKING.LST file lists the files supplied and the diskettes and
- subdirectories where they reside.
-
- OUTLINE OF THIS FILE
-
- Compiler Versions and Memory Models Supported
- Manual Changes
- Warnings and Usage Notes
- Troubleshooting
- Extracting the Source Code
- Printing the Source Code
- Removing Tabs From the Source Code
- Rebuilding the Libraries
- Rebuilding the Sample Programs
- C and Assembly Modules and Macros
- Construction Notes
-
- COMPILER VERSIONS AND MEMORY MODELS SUPPORTED
-
- This version of Turbo C TOOLS supports Turbo C versions 1.00, 1.50, and 2.00.
- For information about later versions of the Turbo C compiler, check the
- bulletins enclosed with Turbo C TOOLS or contact Blaise Computing.
-
- Tiny (T) model: Turbo C TOOLS does not officially support the T model.
- However, many modules in the S model library (TCT_T2S.LIB) will work
- correctly in T model programs.
-
- Huge (H) model: For many programs using the H model, you can use the L model
- library (TCT_T2L.OBJ), especially if they contain no interrupt service
- routines (ISRs) or intervention code. However, if you need support for data
- objects larger than 65,535 bytes or if your program malfunctions, then
- recompile the library using the H memory model. See "Rebuilding the
- Libraries" below.
-
- The following files are specific to particular memory models. The same files
- support Turbo C versions 1.00, 1.50, and 2.00, with a few exceptions listed
- below under "Warnings and Usage Notes". The columns of the table are
- explained below.
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 1
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- "Native "No Mouse
- Memory Model Library Windows" COMPILER.MAC Support"
- ------------ ----------- ---------- ------------ ------------
- S TCT_T2S.LIB NW_T2S.OBJ COMP_T2S.MAC BNOMOUSE.OBJ
- M TCT_T2M.LIB NW_T2M.OBJ COMP_T2M.MAC BNOMOUSE.OBJ
- C TCT_T2C.LIB NW_T2C.OBJ COMP_T2C.MAC BNOMOUSE.OBJ
- L TCT_T2L.LIB NW_T2L.OBJ COMP_T2L.MAC BNOMOUSE.OBJ
-
- Memory Model: This affects the maximum data and code size in your program
- and the nature of data and code pointers. In the Turbo C Integrated
- Environment (TC.EXE), the memory model is specified via the
- Options/Compiler/Model switch; the default is S model unless you save a
- different configuration. With the command-line version (TCC.EXE), the
- memory model is specified via the /m command line switch; the default is S
- model.
- Library: These files are precompiled versions of all the Turbo C TOOLS
- functions. To link them into your programs, specify the proper library
- file on the compiler or linker command line or in your project file.
- "Native Windows" file: Programs linked with this optional object file
- coordinate all their Turbo C TOOLS window operations with the Turbo C text
- window. This object file requires Turbo C version 1.50 or later. Read
- the section on "Turbo C's Text Window" in the chapter on window functions
- (prefix WN).
- COMPILER.MAC file: This specifies the memory model for Turbo C modules
- written in assembly language. If you reassemble any Turbo C assembler
- modules, first copy the correct file to COMPILER.MAC.
- "No Mouse Support" file: Programs linked with BNOMOUSE.OBJ are prevented
- from including the mouse functions MOCHECK, MOHIDE, and MOPRECLK. If your
- program uses menus, WNREAD, or the help system, and if you don't want to
- use the mouse, then linking with BNOMOUSE.OBJ will make your program
- slightly smaller. Notice that the same BNOMOUSE.OBJ file supports all
- memory models.
-
- MANUAL CHANGES
-
- The following are important changes to the manual. The changes have already
- been made in the online reference database.
-
- Pages 36 (WNEXAMPL.C) and 54 (MNEXAMPL.C) -- The constants CYAN and MAGENTA
- should be replaced by SC_CYAN and SC_MAGENTA, respectively.
- Page 60 -- The MN_NOWRAP action bit has been added. Its bit value is 0x4000.
- It has the effect of suppressing wraparound for the MN_UP, MN_DOWN,
- MN_RIGHT, MN_LEFT, MN_NEXT, and MN_PREVIOUS motions.
-
- The following motions have been added:
-
- Symbol Value Motion
- ---------- ----- ------------------------------------------
- MN_PGUP 0x00a Move upward the height of the viewport.
- MN_PGDN 0x00b Move downward the height of the viewport.
- MN_PGRIGHT 0x00c Move rightward the width of the viewport.
- MN_PGLEFT 0x00d Move leftward the width of the viewport.
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 2
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- Page 61 -- The following default key assignments have been added:
-
- Keystroke ASCII value Key code Action(s) Motion
- ---------------- ----------- -------- --------- -----------
- PgUp 0 73 MN_PGUP
- PgDn 0 81 MN_PGDN
- Ctrl-right arrow 0 116 MN_PGRIGHT
- Ctrl-left arrow 0 115 MN_PGLEFT
-
- Enhanced Keyboard:
-
- PgUp 224 73 MN_PGUP
- PgDn 224 81 MN_PGDN
- Ctrl-right arrow 224 116 MN_PGRIGHT
- Ctrl-left arrow 224 115 MN_PGLEFT
- Enter 13 224 MN_TRANSMIT
-
- Page 75 -- The sample help source file you should study is SHOWHELP.TXT.
- SHOWHELP.HLP is its binary version.
- Page 126 -- To use malloc() inside a TSR program, you can use a new function
- called ISRESERV instead of the cumbersome method described in the manual.
- Read the description of ISRESERV in the ISRESERV.DOC file or in the online
- reference database.
-
- ISRESERV is useful for the near heap in the T, S, and M memory models and
- the far heap in the C, L, and H models. To reserve space on the far heap
- in the T, S, and M models, create a new function based on ISRESERV.C and
- in the new function replace malloc() and free() with farmalloc() and
- farfree(), respectively.
- Page 156 (EDFIELD) -- There is an additional fifth argument: "pfinal". The
- calling sequence now is:
-
- int edfield(const char *pinitstr,
- char *pretstr,
- int retsize,
- const ED_CONTROL *pctrl,
- KEY_SEQUENCE *pfinal);
-
- "pfinal" is the address of a structure in which to report the final
- keystroke, or NIL if no report is desired.
- Pages 183 (HLDISP) and 190 (HLREAD) -- If the "pfinal" argument is the NIL
- pointer, then no information is returned via "pfinal", and the returned
- value of the function is always NIL, regardless of whether an error is
- detected.
- Pages 231 (KBQUERY) and 467 (WNQUERY) -- The value returned in *pkey has
- changed: now it is always the key code (scan code) of the terminating
- keystroke. The value of the function is always the character code of the
- terminating keystroke.
- Pages 254 (MNDSTROY) and 480 (WNREMOVE) -- When setting the Turbo C text
- window to the entire screen, the text color is not changed. Therefore the
- text color may remain the same as the last selected window.
- Page 371 (STPEXPAN) -- None of its arguments should have the "const"
- modifier.
- Page 412 (UTSQZSCN) -- The data type of the "psource" argument is now "const
- char far *".
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 3
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- Page 421 (UTUNSQZ) -- The data type of the "psource" argument is now "const
- char *".
- Page 454 (WNFIELD) -- WNFIELD returns an immediate error if any portion of
- the window's viewport is covered by any other viewport. There is an
- additional sixth argument: "pfinal". The calling sequence now is:
-
- int wnfield(BWINDOW *pwin,
- const char *pinitstr,
- char *pretstr,
- int retsize,
- const ED_CONTROL *pctrl,
- KEY_SEQUENCE *pfinal);
-
- "pfinal" is the address of a structure in which to report the final
- keystroke, or NIL if no report is desired.
- Page 472 (WNREAD) -- A new argument called "pfinal" has been added. The
- calling sequence is now as follows:
-
- WN_EVENT *wnread(BWINDOW *pwin,
- const WHERE *pwhere,
- int view_ht, int view_wid,
- int org_row, int org_col,
- const BORDER *pbord,
- WN_EVENT *pfinal,
- int option);
-
- "pfinal" is the address of a structure to receive a copy of the final
- event the user performed, or NIL if no copy is desired. The returned
- value of the function is also changed: it is a copy of "pfinal", or NIL
- if failure.
- Page 533 -- Change in behavior for global variable b_ega: After you call
- SCEQUIP, the b_ega global variable will contain the value SC_ABSENT (-2)
- if a Video Graphics Array (VGA) or PS/2 Display Adapter is installed.
- Under Turbo C TOOLS version 5, b_ega would contain SC_MONO (0) or SC_COLOR
- (1) if a VGA was present because the VGA emulates all the EGA's
- functionality.
- Page 534 -- Internal functions with changed calling sequences include
- MNTRUNC, WNNUPBLK, WNPIMBLK, and WNPUTIMG.
- Page 538 -- The "EB" notation marks new keystrokes that are translated by the
- traditional BIOS services into their traditional equivalents, as well as
- keystrokes that are discarded by the traditional BIOS services.
- Page 556 -- The global variables b_mnmohoriz and b_mnmovert report the
- character column and row (respectively) where the final mouse event took
- place under MNREAD or MNLREAD. They are expressed in terms of character
- cells, not pixels. They contain 0xffff if the final event was a
- keystroke.
- Page 562 -- New internal function: WNSETATR sets the Turbo C text window's
- attribute.
-
- WARNINGS AND USAGE NOTES
-
- STACK CHECKING IN ISRs -- Stack overflow checking is not permitted in either
- interrupt service routines (ISRs) or intervention functions in the T, S,
- and M memory models of Turbo C version 2.00 and later. Stack checking is
- also prohibited in all functions called by the affected ISRs and
- intervention functions. (Note: Stack checking occurs only if you set the
-
-
- Blaise Computing Inc. March 31, 1989 Page 4
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- O/C/Code/Test Stack option (in the Integrated Environment) or specify the
- -N command line option when compiling your program.)
- FLPROMPT AND MOCHECK UNDER TURBO C 1.0 -- If your program uses FLPROMPT or
- MOCHECK under Turbo C version 1.0, then you should recompile FLPROMPT.C
- and/or MOCHECK.C under version 1.0 and link with the resulting .OBJ
- file(s). (MOCHECK is used to detect mouse clicks and is used in HLDISP,
- HLREAD, MNREAD, and WNREAD. MOCHECK is suppressed if you link with
- BNOMOUSE.OBJ.)
- INTERVENTION CODE ON DOS VERSION 2 -- Please read "Foreground and Background
- Programs and Their Privileges" on page 122 of the Turbo C TOOLS Reference
- Manual. The intervention scheduler does not set the current process on
- DOS version 2. Therefore, intervention functions in background programs
- on DOS version 2 should avoid DOS memory allocation. In addition, they
- should open and reclose their files each time they are invoked.
- INTERVENTION CODE ON NON-IBM VERSIONS OF DOS -- If you specify IV_DOS_NEED
- when installing an intervention function, the scheduler will postpone
- invoking the intervention function if an interrupt 0x24 (critical error)
- is in progress. The location of the interrupt 0x24 busy flag varies
- between different versions of DOS. If you encounter a problem using
- intervention code on a non-IBM version of DOS, please contact Blaise
- Computing.
- SCROLLING MONOCHROME DISPLAY PAGES -- The BIOS scroll function normally
- obtains the attribute for the new blank rows by examining the previous
- location of the cursor. The Enhanced Graphics Adapter supports multiple
- display pages on the Monochrome Display. On monochrome display pages
- beyond page 0, BIOS scrolling works improperly in that the attribute of
- the new blank rows is obtained from page 0 instead of the active page.
- This affects SCTTYWIN, SCTTYWRT, and VISCROLL.
-
- TROUBLESHOOTING
-
- Please also read Appendix A in the manual. Here are some additional symptoms
- and explanations to consider when diagnosing problems:
-
- Abnormal program termination.
- This can occur if the startup module cannot allocate sufficient space for
- the stack and the near heap. If you are initializing the global variables
- "_stklen" and "_heaplen", try smaller values.
- Text appears in incorrect color.
- When MNDSTROY and WNREMOVE set the Turbo C text window to the entire
- screen, they do not change the text color. Therefore text later emitted
- via the Turbo C text window functions may have the colors of the last
- selected window.
- Asynch overruns during mouse operations.
- Since the Microsoft mouse operates via hardware interrupts, it is possible
- that mouse movements and button presses and releases will cause overrun
- errors during the arrival of data at the serial ports. First test whether
- overruns occur without the use of Turbo C TOOLS. The internal function
- MOCATCH disables interrupts for a significant period of time; this
- function is installed when you use HLDISP, HLREAD, MOCHECK, MNREAD, or
- WNREAD. If overruns are a severe problem, contact Blaise Computing.
-
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 5
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- EXTRACTING THE SOURCE CODE
-
- The source code for the library is supplied in the form of two
- self-extracting archive programs: TCTSRC1.EXE and TCTSRC2.EXE. The full
- contents of both files are listed in the PACKING.LST file.
-
- To extract the contents of either file, set the current drive and directory
- to the drive and directory where you want to put the files. Then execute the
- self-extracting archive program, as in the following example:
-
- a:tctsrc1
-
- To extract only a selection of the files in an archive, you can use ambiguous
- filenames, as in the following example, which extracts all the source code
- for the window (WN) functions:
-
- a:tctsrc2 wn*.*
-
-
- PRINTING THE SOURCE CODE
-
- The CONCAT.COM utility for printing the source code is described in the
- manual's chapter on "Using Turbo C TOOLS". As an additional aid, lists are
- provided for each category of source files. For example, the ST.FIL file
- lists all the source files for the string (ST) functions. You can use this
- file when formatting all the ST files as follows:
-
- concat st.prt <st.fil
-
-
- REMOVING TABS FROM THE SOURCE CODE
-
- The source modules were saved with consecutive blank spaces compressed to tab
- characters, with tab stops every eight characters. The EXPAND.COM utility is
- provided to expand the tabs back to blank spaces if you wish. It is also
- useful for removing tabs from help source files.
-
- EXPAND is a filter: it obtains its input from the standard input device and
- writes its output to standard output. Therefore you can use it by
- redirecting standard input and output, as in the following example:
-
- expand <wnexampl.c >wnexampl.ntb
-
- The resulting file WNEXAMPL.NTB has tab characters expanded to strings of
- blanks.
-
- REBUILDING THE LIBRARIES
-
- A batch file, BUILDLIB.BAT, and a librarian response file, LIBRESP, are
- provided to make it easy to reconstruct the Turbo C TOOLS libraries. The
- batch file makes a number of assumptions. If these are not appropriate for
- your environment, you should alter the batch file to match your system. The
- assumptions are:
-
- All source files (.C and .ASM) and the LIBRESP file are in the current
- directory;
-
-
- Blaise Computing Inc. March 31, 1989 Page 6
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- BEGINASM.MAC and COMP_T2?.MAC are in the MAC subdirectory;
- The C language header files (.H) are in the \TURBOC\INCLUDE directory;
- The Turbo C command-line compiler (TCC.EXE), the Turbo Assembler
- (TASM.EXE), and the Turbo Librarian (TLIB.EXE) are either in the
- current directory or in one of the directories specified in the PATH=
- environment entry.
-
- BUILDLIB is invoked with the command
-
- buildlib model
-
- where "model" is either s, m, c, l, or h (in lower case) to indicate the
- memory model. The batch file compiles and assembles all source modules by
- category (to make it easy for you to recompile just some categories), and
- then invokes the librarian to create the library. For example, to
- reconstruct the small memory model library, issue the command
-
- buildlib s
-
-
- REBUILDING THE SAMPLE PROGRAMS
-
- The MAKEXPLS file is designed for use with the Turbo MAKE utility to rebuild
- the eighteen sample programs. It makes the following assumptions:
-
- The sample program source files are in the current directory.
- All Turbo C and Turbo C TOOLS header files are in the \TURBOC\INCLUDE
- directory.
- All libraries are in the \TURBOC\LIB directory.
- The Turbo C command-line compiler (TCC.EXE) and the Turbo Linker
- (TLINK.EXE) are either in the current directory or in one of the
- directories listed in the PATH= environment entry.
- For rebuilding TCWIN.EXE, the batch file MAKTCWIN.BAT must be either in
- the current directory or in one of the directories listed in the PATH=
- environment entry; also the proper NW_T2?.OBJ file must be in the
- \TURBOC\LIB directory.
-
- Invoke the make file by issuing the following command to rebuild a single
- example program
-
- make -fmakexpls mnexampl.exe
-
- or the following command to rebuild all eighteen:
-
- make -fmakexpls
-
-
-
-
-
-
-
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 7
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- C AND ASSEMBLY MODULES AND MACROS
-
- The following tables list which functions are implemented in C, which in
- assembly language, and which are macros defined in the header files. The
- tables also list certain anomalous source files.
-
- The following functions are implemented as ordinary C functions, each in its
- corresponding .C file:
-
- edbase isprep mnhilit0 mospeed scttywin wnchgevn wnremevn
- edbuffer isremove mnhilite mostat scttywrt wncover wnremove
- edchgkey isreserv mnitem prcancel scwrap wncreat0 wnresprv
- edinitky issense mnitmkey prerror scwrite wncurmov wnretevn
- edreduce ivdetect mnkey prgetq stpcvt wncurpos wnretinf
- edremkey ivdisabl mnlitem prinstld stpexpan wncurset wnrevupd
- edretinf ivinstal mnlitkey prspool stpjust wncursor wnscrblk
- edretkey ivsense mnmchitm scapage stptabfy wncurtrk wnscrlbr
- edsetcur ivvecs mnmchkey scattrib stpxlate wndstroy wnscroll
- edwrap kbequip mnmouse scblink stschind wnerror wnseldev
- edwrrect kbextend mnmstyle scborder utansi wnforget wnselect
- edzapkey kbflush mnread scbox utcrit wngetimg wnsetbuf
- fldolock kbgetkey mnvalmn0 scchgdev utctlbrk wngetopt wnsetcur
- flflush kbkcflsh mnvdisp scclrmsg utgetclk wnhide wnsetopt
- flgetdta kbpoll moavoid sccurset utmovmem wnhoriz wnshoblk
- fllock kbquery mobutton sccurst utnulchk wninitev wnunhide
- flnorm kbqueue mocheck scequip utsafcpy wnneedup wnupdate
- flprompt kbset mocurmov scgetvid utsleep wnnupblk wnvalev0
- flputdta kbstuff moequip scmode utspkr wnorigin wnvalno0
- flremvol kbwait mogate scmode4 utsqzscn wnovrlap wnvalwi0
- flretvol mmctrl mogetmov scnewdev uttim2tk wnpgadd wnvdisp
- flsetvol mmfirst mograph scpages uttk2tim wnpgrem wnwrap
- hlclose mmsize mohandlr scpal1 utunsqz wnpimblk wnwrbuf
- hldisp mnatr mohard scpalett viatrect wnpoll wnwrrect
- hlfrindx mncreat0 mohide scpclr vihoriz wnprintf wnwrstrn
- hllookup mndefkey moinst scpgcur viptr wnputbor wnwrttyx
- hlopen mndisabl mojump scread virdsect wnputsen wnzapevn
- hlpas2c mndlitms molitpen screstpg viscroll wnquery wnzapsen
- hlread mndlkeys mopreclk scrows viwrsect wnrdbuf
- iscurprc mndstroy morange scsavepg wnatrblk wnread
- isinstal mnfindsl mosoft scsetvid wnatrstr wnredraw
-
- The following functions are implemented in assembly language, each in its
- corresponding .ASM file:
-
- iscall ivctrl kbready utamove utmodel
- isdispat kbplace mocatch utintflg vidirec0
-
-
-
-
-
-
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 8
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
- The following routines are implemented as macros, defined in the header files
- shown here:
-
- Macro Definition | Macro Definition | Macro Definition
- -------- ---------- | ---------- ---------- | -------- ----------
- edfield bedit.h | utdosmajor butil.h | utpokeb butil.h
- isgetvec bintrupt.h | utdosminor butil.h | utpoken butil.h
- isputvec bintrupt.h | utdosrdy butil.h | utpokew butil.h
- isresext bintrupt.h | utdosver butil.h | utpspseg butil.h
- kbscanof bkeybrd.h | uthibyte butil.h | utrange butil.h
- kbstatus bkeybrd.h | uthinyb butil.h | utseg butil.h
- max butil.h | uthiword butil.h | utsign butil.h
- min butil.h | utinp butil.h | utskip butil.h
- mncreate bmenu.h | utintoff butil.h | utsound butil.h
- mndsplay bmenu.h | utinton butil.h | utspkoff butil.h
- mnlread bmenu.h | utlobyte butil.h | utspkon butil.h
- moreset bmouse.h | utlonyb butil.h | uttofar butil.h
- prchar bprint.h | utlowlim butil.h | uttofaru butil.h
- prinit bprint.h | utloword butil.h | utuplim butil.h
- prstatus bprint.h | utmax butil.h | utwdlong butil.h
- scclrmsg bscreens.h | utmin butil.h | vidspmsg bvideo.h
- scpage bscreens.h | utnorm butil.h | virdrect bvideo.h
- utabs butil.h | utnybbyt butil.h | viwrrect bvideo.h
- utalarm butil.h | utoff butil.h | wnattr bwindow.h
- utalloc butil.h | utoutp butil.h | wncreate bwindow.h
- utbound butil.h | utpeekb butil.h | wndsplay bwindow.h
- utbyword butil.h | utpeekn butil.h | wnfield bwindow.h
- utchknil butil.h | utpeekw butil.h | wnwrstr bwindow.h
- utcopy butil.h | utplong butil.h | wnwrtty bwindow.h
-
- The following functions do not have their own source files, but are defined
- in the source files shown here:
-
- Function Defined | Function Defined
- -------- ---------- | -------- ----------
- b_vidcpy scnewdev.c | ivdisk ivctrl.asm
- ivbiosky ivctrl.asm | ivdos ivctrl.asm
- ivcbreak ivctrl.asm | ividle ivctrl.asm
- ivcom1 ivctrl.asm | ivkeybd ivctrl.asm
- ivcom2 ivctrl.asm | ivtimer ivctrl.asm
-
- The following source files are not named for any individual function:
-
- BNOMOUSE.ASM defines substitute versions of MOCHECK, MOHIDE, and MOPRECLK.
- See the section "Excluding Mouse Support" in the chapter on mouse
- support functions (prefix MO).
- NW.C defines versions of WNCHKDM, WNCMOVE, WNGETATR, WNSETATR, and
- WNSETWIN that make contact with the Turbo C text window. NW.C is the
- source module for the NW_T2?.OBJ files.
- WNNATVWN.C defines versions of WNCHKDM, WNCMOVE, WNGETATR, WNSETATR, and
- WNSETWIN that do not use the Turbo C text window. It is the source
- file for the WNNATVWN.OBJ modules in the libraries.
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 9
-
-
-
-
- Turbo C TOOLS/2.0 Version 6.00
-
-
-
- The following source files define no functions:
-
- KBSCANOF.C defines the b_keycod[] array, which is referenced by the
- KBSCANOF macro.
- MOVARS.C defines the global variables b_mocatch, b_modispat, b_mohanmask,
- and b_momask.
- SCPAGE.C defines the b_curpage global variable, which is referenced by the
- SCPAGE macro.
-
- CONSTRUCTION NOTES
-
- All C modules and example programs were compiled with version 2.0 of the
- Turbo C command-line compiler (TCC) using the following switches: -c
- (compile only), -m (memory model), -O (optimize jumps), and -w (enable all
- warnings). All assembler modules were assembled with version 1.0 of the
- Turbo Assembler (TASM) using the /mx and /w+ switches. The libraries were
- built with version 2.0 of the Turbo Librarian (TLIB) using the /0 switch.
- (The /0 librarian switch omits unnecessary debugging and autodependency
- information.)
-
- The example programs were linked with TLINK version 2.0 using no switches.
-
-
- (For a list of supplied files and the diskettes and subdirectories where they
- reside, see the PACKING.LST file.)
-
- === End of README.DOC ===
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Blaise Computing Inc. March 31, 1989 Page 10
-
-
-