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

 Using libraries
------------------------------------------------------------------------------
 A library is simply a file containing a collection of pre-compiled routines
 (.OBJ files), usually with an attached index. It is created by a library
 manager utility such as Microsoft's LIB.EXE, which allows the addition,
 deletion and extraction of object modules from the library.

 The main advantage of libraries over object modules from the developer's
 perspective, is that only the required modules are brought in from a
 library, whereas an object module is always included in the program whether
 it is needed or not. The use of libraries keeps the size of the final
 program down, without the developer having to determine which particular
 library modules are required by the program.
 Normally there are three sources of libraries which a developer may choose:

 . Compiler language libraries
 . Third party libraries
 . In-house libraries

 It is often the case that compiler language libraries are non-overlayable,
 for two reasons. Firstly, the type of code they contain is often highly
 optimized assembler and may use many near calls, which are non-overlayable.
 Secondly, it is not usually desirable to overlay extremely frequently used
 routines such as these, since program performance may suffer. Exceptions to
 this general rule are the CA-Clipper libraries, significant portions of
 which are written in large model C, and can be successfully overlaid.

 Third party add on libraries are available for many compilers / languages,
 and generally add functionality not provided by the compiler vendor, such as
 graphics or communications. The major benefit of using third party libraries
 is in reduced development time at nominal cost compared with the amount of
 time, effort, and expertise required to duplicate a library's functionality
 in-house.

 In-house libraries may contain virtually anything the developers feel may be
 useful across several projects, and often contain code that allows
 developers to maintain an in-house style or standard interface.

 During the link, Blinker will extract from each library only those routines
 which are needed by the program for its execution.