CONTENTS
___________________________________________________________________________





                                           Linker response files . . . . 28
HOW TO USE THIS FILE . . . . . . . 1     Sample OBJXREF reports  . . . . 28
BGIOBJ: Converting graphics drivers        Report by public names
and fonts  . . . . . . . . . . . . 2       (/RP) . . . . . . . . . . . . 29
  Adding the new .OBJ files to             Report by module (/RM)  . . . 29
  GRAPHICS.LIB . . . . . . . . . . 3       Report by reference (/RR) . . 30
  Registering the drivers and              Report by external references
  fonts  . . . . . . . . . . . . . 3       (/RX) . . . . . . . . . . . . 30
    An example . . . . . . . . . . 4       Report of module sizes
  The /F option  . . . . . . . . . 5       (/RS) . . . . . . . . . . . . 31
  Advanced features  . . . . . . . 6       Report by class type (/RC)  . 31
CPP: The preprocessor  . . . . .  10       Report of unreferenced symbol
  CPP as a macro preprocessor  .  11       names (/RU) . . . . . . . . . 32
  An example . . . . . . . . . .  11       Verbose reporting (/RV) . . . 32
GREP: A text-search utility  . .  12     Examples of how to use
  Command-line syntax  . . . . .  13     OBJXREF . . . . . . . . . . . . 32
  GREP options . . . . . . . . .  13       Example 1 . . . . . . . . . . 32
    Order of precedence  . . . .  16       Example 2 . . . . . . . . . . 33
  The search string  . . . . . .  16       Example 3 . . . . . . . . . . 33
    Operators in regular                   Example 4 . . . . . . . . . . 33
    expressions  . . . . . . . .  17     OBJXREF error messages and
  File specifications  . . . . .  18     warnings  . . . . . . . . . . . 34
  Some GREP examples . . . . . .  18       Error messages  . . . . . . . 34
    Example 1  . . . . . . . . .  18       Warnings  . . . . . . . . . . 34
    Example 2  . . . . . . . . .  19   PRJCFG: Configuration file
    Example 3  . . . . . . . . .  19   utility . . . . . . . . . . . . . 35
    Example 4  . . . . . . . . .  20   PRJCNVT: Old projects for new . . 35
    Example 5  . . . . . . . . .  20   PRJ2MAK: From project file to MAKE
    Example 6  . . . . . . . . .  21   file  . . . . . . . . . . . . . . 36
    Example 7  . . . . . . . . .  21   THELP: The Turbo Help utility . . 37
    Example 8  . . . . . . . . .  22     Loading and invoking THELP  . . 37
OBJXREF: The object module cross-        Navigating THELP  . . . . . . . 38
reference utility  . . . . . . .  22     THELP options . . . . . . . . . 39
  The OBJXREF command line . . .  23       /C#xx (select color)  . . . . 40
    The OBJXREF command-line               /Fname (full path and name for
    options  . . . . . . . . . .  24       help file)  . . . . . . . . . 41
      Control options  . . . . .  24       /H, /?, and ? (display help
      Report options . . . . . .  25       screen) . . . . . . . . . . . 42
  Response files . . . . . . . .  27       /Kxxyy (reassign hot key) . . 42
    Free-form response files . .  27       /U (remove THELP from
    Project files  . . . . . . .  27       memory) . . . . . . . . . . . 43



                                     i






    /Wx,y,w,h (set the window size     TRANCOPY: A project transfer item
    and location)  . . . . . . .  43   utility . . . . . . . . . . . . . 52
TLIB . . . . . . . . . . . . . .  43   TRIGRAPH: A character-conversion
  Why use object module                utility . . . . . . . . . . . . . 53
  libraries? . . . . . . . . . .  44   Transfer macros . . . . . . . . . 54
  The TLIB command line  . . . .  44         State macros  . . . . . . . 54
    The operation list . . . . .  46         File name macros  . . . . . 54
      File and module names  . .  46         Instruction macros  . . . . 55
      TLIB operations  . . . . .  46     Running DOS commands  . . . . . 59
  Using response files . . . . .  48     Transfer memory settings  . . . 59
  Creating an extended dictionary:     Turbo Editor macros . . . . . . . 60
  The /E option  . . . . . . . .  49   TEMC command line . . . . . . . . 60
  Setting the page size: The /P        Syntax  . . . . . . . . . . . . . 61
  option . . . . . . . . . . . .  49   Key codes . . . . . . . . . . . . 62
  Advanced operation: The /C             Named keys  . . . . . . . . . . 63
  option . . . . . . . . . . . .  50   Predefined editor commands  . . . 64
  Examples . . . . . . . . . . .  51
TOUCH  . . . . . . . . . . . . .  51   Index                             77

































                                    ii






TABLES
___________________________________________________________________________





1.1: Summary of THELP command-line     1.3: TLIB action symbols  . . . . 47
     options . . . . . . . . . . .39   1.4: TEMC editor commands . . . . 64
1.2: TLIB options  . . . . . . . .45









































                                    iii












Online document
___________________________________________________________________________



                                                            Other utilities




===========================================================================
HOW TO USE THIS FILE
===========================================================================

                    This file has a table of contents and an index that
                    refer to "pages" in this file. If your editor has a
                    search facility, you can use it to search for the page
                    numbers listed in either the table of contents or in
                    the index. The text "- n -" (where n represents the
                    actual page number) appears at the bottom left of the
                    "page" it refers to. Thus, at the bottom of page 1,
                    you'll find "- 1 -" as the last item on that "page."

                    Turbo C++ comes with a host of standalone utilities
                    that you can use with your Turbo C++ files or other
                    modules. Several are documented in the User's Guide;
                    others are documented here.


                    -------------------------------------------------------
                    Name       Description
                    -------------------------------------------------------

                    Documented in the User's Guide

                    MAKE       Standalone program manager
                    TLINK      Turbo Linker

                    Documented in this file

                    BGIOBJ     Conversion utility for graphics drivers and
                               fonts



                                   - 1 -






                    CPP        Preprocessor
                    GREP       File-search utility
                    OBJXREF    Object module cross-referencer
                    PRJCFG     Updates options in a project file from a
                               configuration file, or converts a project
                               file to a configuration file
                    PRJCNVT    Converts Turbo C project files to the Turbo
                               C++ format
                    PRJ2MAK    Converts Turbo C++ project files to MAKE
                               files
                    THELP      Turbo Help utility
                    TLIB       Turbo Librarian
                    TOUCH      Updates file date and time
                    TRANCOPY   Copies transfer items from one project to
                               another
                    TRIGRAPH   Character-conversion utility
                    TEML/TEMC  Turbo Editor Macro Language and Compiler

                    -------------------------------------------------------

                    This file explains what each utility is and
                    illustrates, with code and command-line examples, how
                    to use them.



===========================================================================
BGIOBJ: Converting graphics drivers and fonts
===========================================================================

                    You can use BGIOBJ to convert graphics driver files and
                    character sets (stroked font files) to object (.OBJ)
                    files. Once they're converted, you can link them into
                    your program, making them part of the executable file.
                    This is in addition to the graphics package's dynamic
                    loading scheme, in which your program loads graphics
                    drivers and character sets (stroked fonts) from disk at
                    run time.

                    Linking drivers and fonts directly into your program is
                    advantageous because the executable file contains all
                    (or most) of the drivers and/or fonts it might need,
                    and doesn't need to access the driver and font files on
                    disk when running. However, linking the drivers and
                    fonts into your executable file increases its size.






                                   - 2 -






                    To convert a driver or font file to a linkable object
                    file, use the BGIOBJ.EXE utility. This is the
                    simplified syntax:

                      BGIOBJ source_file

                    where source_file is the driver or font file to be
                    converted to an object file. The object file created
                    has the same file name as the source file, with the
                    extension .OBJ; for example, EGAVGA.BGI yields
                    EGAVGA.OBJ, SANS.CHR gives SANS.OBJ, and so on.


    Adding the new  =======================================================
     .OBJ files to
      GRAPHICS.LIB  You should add the driver and font object modules to
                    GRAPHICS.LIB, so the linker can locate them when it
                    links in the graphics routines. If you don't add these
                    new object modules to GRAPHICS.LIB, you'll have to add
                    them to the list of files in the project (.PRJ) file,
                    on the TCC command line, or on the TLINK command line.
                    To add these object modules to GRAPHICS.LIB, invoke
                    TLIB with the following command line:

                      tlib graphics + object_file_name [+ object_file_name
                    ...]

                    where object_file_name is the name of the object file
                    created by BGIOBJ.EXE (such as CGA, EGAVGA, GOTH, and
                    so forth). The .OBJ extension is implied, so you don't
                    need to include it. You can add several files with one
                    command line to save time; see the example in the
                    following section.


   Registering the  =======================================================
 drivers and fonts
                    After adding driver and font object modules to
                    GRAPHICS.LIB, you have to register all the drivers and
                    fonts that you want linked in; you do this by calling
                    registerbgidriver and registerbgifont in your program
                    (before calling initgraph). This informs the graphics
                    system of the presence of those files, and ensures that
                    they will be linked in when the executable file is
                    created by the linker.