Changing existing code for the shared library
All C code that works in a shared library will also
work in a non-shared library.
However, the reverse is not true
because a shared library must explicitly handle imported symbols.
The following guidelines are meant to help you produce shared library code
that is still valid for non-shared libraries
(although it may be slightly bigger and slower).
The guidelines
explain how to structure data for ease of maintenance,
since most compatibility problems involve restructuring data.
Next topic:
Minimize global data
Previous topic:
Include routines the library itself needs
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003