On Wed, 11 Apr 2007 08:51:29 -0700 Mark Crispin <[EMAIL PROTECTED]> wrote:
MC> It is axiomatic that, whether shared or static library, the .h files used MC> to build an application for a library should correspond to the library. MC> I've seen cases where shared libraries did not correspond to the .h files; This can happen for the static library too and there is a standard way to prevent this from happening: define the version constants in the library header file and require the user code to pass them to the library initialization function. Then, if they don't match, do whatever is necessary (which could well be nothing if the run-time library version is known to be compatible with the -- older -- version used for the user application compilation, or a failure to initialize the library if a real mismatch is detected). Of course, this does assume that the versions are updated and it's always possible to devise a fool such that this scheme is not fool-proof enough to help. But in practice this detects accidental mismatches pretty well. Regards, VZ _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
