Go to the first, previous, next, last section, table of contents.


4.5 Object Code and Archives

The library of practical abstractions provides two versions of all object code: safe and unsafe. We recommend the routine use of safe object code. Safe object code is intended for everyday use. Safe object code has been compiled with no optimizations, with all assert() macros, and with full symbol tables for debugging. Safe libraries are named `libmodule.a'. The `libpa.a' archive includes all safe object code in the current release.

Unsafe object code is intended for more demanding applications. Unsafe object code has been compiled with maximum optimizations, the NDEBUG macro defined, and without any symbol tables. We discourage the routine use of unsafe object code, which is why we gave it such a frightful name. Under no conditions should unsafe object code be used during debugging, because optimizations are a major source of compiler errors and erroneous debugger information as well. Unsafe libraries are named `libmodule_u.a'. The `libpa_u.a' archive includes all unsafe object code in the current release.


Go to the first, previous, next, last section, table of contents.