Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!uw-june!ka
From: ka@uw-june.UUCP
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries
Message-ID: <3172@uw-june.UUCP>
Date: Sun, 27-Sep-87 15:53:53 EDT
Article-I.D.: uw-june.3172
Posted: Sun Sep 27 15:53:53 1987
Date-Received: Sun, 27-Sep-87 23:37:07 EDT
References: <6886@eddie.MIT.EDU) <2501@xanth.UUCP> <2067@sfsup.UUCP> <2903@phri.UUCP>
Organization: U of Washington, CSCI, Seattle
Lines: 13
Xref: utgpu comp.arch:2255 comp.unix.wizards:4230 comp.os.misc:234

> What do I do on a shared library system when scanf changes out from
> under me and breaks my program?

You recompile your program to use the old version of the shared library
instead of the current one.  Sure, it would be nice not to have to
recompile these programs, but in the case of nonshared libraries you
have to recompile also.  With nonshared libraries, you would have to
recompile all the programs which were broken due to the bug in scanf.
With shared libraries, on the other hand, you have to recompile the
programs that depend upon the bug in scanf.  However, these programs
should really be fixed, which will force them to be recompiled anyway.
				Kenneth Almquist
				uw-june!ka	(New address!)