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

 In This Chapter
------------------------------------------------------------------------------

     This chapter covers compiling and linking non-CA-Clipper modules into a
     CA-Clipper application linked with CA-Clipper/ExoSpace.

     Important!  CA-Clipper/ExoSpace is specifically designed for use
     with CA-Clipper applications and cannot be used to generate applications
     written in other languages.  However, CA-Clipper/ExoSpace supports all
     of the CA-Clipper Application Programmer Interfaces (APIs)--Extend,
     FILESYS, GT, ITEM, RDD, and VM.  Modules written in C and Assembler that
     make use of and conform to these APIs will work with CA-Clipper/ExoSpace
     applications, if they do not violate any protected-mode rules.  This
     chapter describes how to compile and link such modules.

     The following compilers are covered in this chapter:

     .  Microsoft C

     .  Microsoft Assembler

     .  Borland C++

     Other languages and compilers that are ordinarily compatible with
     CA-Clipper, such as FORTRAN and Pascal, will also work if compiled
     correctly, if none of the rules of protected-mode programming are
     violated, and if you do not use incompatible runtime library routines as
     described in the following section.

     Note:  The procedures in this chapter assume that you have set up
     the compiler libraries according to the defaults described in the
     runtime library documentation, that the LIB environment variable is set
     to point to the runtime libraries, and that you are not using the
     NODEFLIB (no default libraries) option when you link.

     It is also assumed that the programs being compiled do not violate any
     of the rules of protected-mode programming.  See the "Protected Mode"
     chapter for more information about these rules.