Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!mizar!jesup
From: jesup@mizar.steinmetz (Randell Jesup)
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries (Was: Re: Big Programs Hurt Performance)
Message-ID: <7435@steinmetz.steinmetz.UUCP>
Date: Wed, 23-Sep-87 02:08:31 EDT
Article-I.D.: steinmet.7435
Posted: Wed Sep 23 02:08:31 1987
Date-Received: Fri, 25-Sep-87 03:54:49 EDT
References: <6886@eddie.MIT.EDU) <2501@xanth.UUCP> <2067@sfsup.UUCP> <2903@phri.UUCP>
Sender: root@steinmetz.steinmetz.UUCP
Reply-To: jesup@sungod.steinmetz.UUCP (Randell Jesup)
Organization: General Electric CRD, Schenectady, NY
Lines: 16
Xref: mnetor comp.arch:2306 comp.unix.wizards:4420 comp.os.misc:214

In article <2903@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>	One thing that has always bothered me about shared libraries (or
>dynamic loading, if you prefer) is the problem of backward compatability.
...
>SunOS-3.2 systems for exactly this reason.  What do I do on a shared
>library system when scanf changes out from under me and breaks my program?
>Roy Smith, {allegra,cmcl2,philabs}!phri!roy

	Take a page from the Amiga Exec (which uses shared libraries for
almost everything.  When opening the shared library, tell it what version
of the library you want.  (And maybe whether you'll accept a newer
version).  This also solves the problem of running a binary that want's
version 33 of a library on a system that is only up to 32, for example.
	Randell Jesup  (Please use one of these paths for mail)
	sungod!jesup@steinmetz.UUCP (uunet!steinmetz!{sungod|crd}!jesup)
	jesup@ge-crd.ARPA