### Example of a Definition File for an Executable Module (OS/2)

     NAME MAIN03 WINDOWCOMPAT

    IMPORTS

       SAMPLE03.nSize

       SAMPLE03.pArray

       SAMPLE03.nSwaps

       SAMPLE03.nCompares

       SAMPLE03.list

       SAMPLE03.bubble

       SAMPLE03.insertion

Note: There is no statement to import the `selection` function because it is imported using #pragma import statement in the source code.

The statements given are as follows:

`NAME MAIN03 WINDOWCOMPAT`
  The NAME statement assigns the name `MAIN03` to the program being defined. If no name is given, the name of the executable module (without the .EXE extension) is used. WINDOWCOMPAT specifies that the program is compatible with the PM environment. The alternatives are NOTWINDOWCOMPAT, which means the program is not compatible with the PM environment, or WINDOWAPI, which means the program uses PM APIs.
`IMPORTS`
  This statement defines the names of functions and variables to be imported for the program. Following the IMPORTS keyword are the import definitions. Each definition consists of the name of the DLL where the function or variable is found and the name of the function or variable. The two names must be separated by a period, and each definition must be entered on a separate line.

  You can also use #pragma import to specify that a function is imported from a DLL. You can use this #pragma directive to import the function by name or by ordinal number.

Module Definition Files