Click above to get retro games delivered to your door ever month!

 @ (script file)
------------------------------------------------------------------------------

 Synopsis

     Specify a script file from which to read link commands.

 Syntax

     @<ScriptFile>

 Example

     @myapp

 Description

     When CA-Clipper/ExoSpace encounters the @ command, it will read
     subsequent link commands from the specified link script file until the
     entire script file has been read.  It will then continue reading
     commands from where it left off.  Script files may be nested (that is, a
     script file can invoke another script file using the @ command).

     A script file might look something like the following:

     #
     # sample.lnk - sample link script for
     # CA-Clipper/ExoSpace
     #
     # To execute, type EXOSPACE @SAMPLE
     #
     # You just need to list required OBJs and
     # libraries. Don't worry about overlays -
     # they're a thing of the past!

     FILE MYPROG
     LIB MYLIB

     # The target .EXE name can be optionally specified
     # using the OUTPUT command as shown below. If you
     # omit the OUTPUT command, the .EXE name will be

     # taken from the first .OBJ listed (e.g., in this
     # case, the name would be MYPROG.EXE)

     OUTPUT MYAPP

     # Remember to ensure that any third-party
     # libraries being linked are compatible with
     # CA-Clipper/ExoSpace

     LIB PWFUNCS, CLASSY, PWKERNEL

     # It must appear before any explicit references to
     # any CA-Clipper libraries.

     LIB EXOSPACE

     # To link in the CA-Clipper debugger,
     # uncomment the following line
     # FILE CLD.LIB