Technical Information
 Some technical information, to any who wants to know about it
------------------------------------------------------------------------------

 Here is some Technical information about the Expand library that you
 might find interesting.

 All Assembly written modules have been Assembled by the Microsoft
 Assembler (MASM.EXE) version 5.10. Former versions of Expand used the
 Turbo Assembler, but I converted to the Microsoft version to remain
 compatible with the Clipper Assembly code, which also uses the Micosoft
 Assembler. Both work perfectly well anyway. No specific options regarding
 code generation have been used, only /w2, which is Warning level 2
 (highest), The CPU test routine is the only one executing some exotic
 (386-Specific) code, when applicable (ie. When testing for the i386
 vs. i486 processor).

 All Clipper code included in the Library has been Compiled with the
 Clipper Compiler version 5.01, vs 1.29, dated April 15th, 1991, Time
 Stamped 03:00. The Compiler switches used to the Clipper code are the
 following: /l /m /v /r /w /n.

 /l     no Line info is required in the Library.
 /m     compiled Module at a time
 /v     not necessary, as PRIVATEs and PUBLICs are not used, but added
        anyway.
 /r     no library Requests need to be embedded, as your sources will do
        that anyway.
 /w     Warnings are always on, and there are none..
 /n     there is no need for an implicit procedure of the Name of the
        source file.

 Finally, the Expand Library is generated using the Microsoft Librarian
 (LIB.EXE) version 3.11. Borland's MAKE utility is used to generate the
 whole Library, but that's not important.

 The Clipper code does NOT contain any INIT FUNCTIONs or PROCEDUREs,
 so no initialisation you can't control is executed. The Evaluation
 version of the Library does contain an INIT FUNCTION, to inform you that
 you are using the Evaluation version of the library, the commercial version
 of the Library is completely free of such things; you have total control
 over the Library.

 The Library is made out of 80 .OBJ files, of which 53
 are written in Assembly (.ASM files) and 27 in Clipper 5.01
 (.PRG files). The multitude of files ensures granularity, so that
 only the routines you effectively use are included in the final
 Exectuable file. An EXPAND.LNK file is provided for the Blinker users,
 so that you may use the Expand library optimised for Speed, by putting
 the frequently used (and small) routines in the root section, and
 allocating the rest to the dynamic overlay area. However, the Expand
 library may safely be ALLOCATEd completely to the Overlay Pool.

 Resuming: The Expand library now has a total of 292 functions available
 for the programmer (306 in Total, ie. 14 Internal functions).  204 of them
 have been written in Assembly, leaving 102 Clipper written functions. The
 ratio Assembly/Clipper functions is thus exactly two to one. No C written
 functions as yet.