Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- CA-Clipper 5.3 . Guide To CA-Clipper - <b>request</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 REQUEST
 Declare a module request list
------------------------------------------------------------------------------
 Syntax

     REQUEST <idModule list>

 Arguments

     <idModule list> is the list of modules that will be linked into the
     current executable (.EXE) file.

 Description

     REQUEST is a declaration statement that defines a list of module
     identifiers to the linker.  Like all other declaration statements, a
     REQUEST statement must be specified before any executable statements in
     either the program file, or a procedure or user-defined function
     definition.

     During the compilation of CA-Clipper source code, all explicit
     references to procedures and user-defined functions are made to the
     linker.  In some instances, within a source file, there may be no
     references made to procedure or user-defined function names until
     runtime.  REQUEST resolves this situation by forcing the named
     procedures or user-defined functions to be linked even if they are not
     explicitly referenced in the source file.  This is important in several
     instances:

     .  Procedures, user-defined functions, or formats referenced with
        macro expressions or variables

     .  Procedures and user-defined functions used in REPORT and LABEL
        FORMs and not referenced in the source code

     .  User-defined functions used in index keys and not referenced
        in the source code

     .  ACHOICE(), DBEDIT(), or MEMOEDIT() user functions

     .  Initialization procedures declared with the INIT PROCEDURE
        statement

     .  Exit procedures declared with the EXIT PROCEDURE statement

     To group common REQUESTs together, place them in a header file and then
     include (#include) the header file into each program file (.prg) that
     might indirectly use them.

 Examples

     .  This example shows a typical header file consisting of common
        REQUESTs for REPORT FORMs:

        // Request.ch

        REQUEST HARDCR
        REQUEST TONE
        REQUEST MEMOTRAN
        REQUEST STRTRAN


See Also: ACHOICE() ANNOUNCE DBEDIT() EXIT PROCEDURE EXTERNAL*

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson