Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!sri-unix!bob@ucla-locus
From: bob@ucla-locus@sri-unix.UUCP
Newsgroups: net.unix-wizards
Subject: Re: another argument against shared libraries
Message-ID: <4236@sri-arpa.UUCP>
Date: Tue, 16-Aug-83 12:17:00 EDT
Article-I.D.: sri-arpa.4236
Posted: Tue Aug 16 12:17:00 1983
Date-Received: Thu, 18-Aug-83 05:51:20 EDT
Lines: 14

From:            Bob English <bob@ucla-locus>

How about providing a loader option that would "compile in" a
specified shared library, thus insulating a program from all
future shared library changes?  If you kept the old versions of
libraries around, you would be able to handle most (if not all)
of the retrofit problems.

Another possible solution is to keep old versions of library
routines around forever, so that old programs find the routines
they expect, and new programs get the new versions.  This might
apply only to genuine revisions, and not to bug fixes.

--bob--