Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!cbosgd!mandrill!abvax!crc
From: crc@abvax.icd.ab.com (Clive R. Charlwood)
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries (Was: Re: Big Programs Hurt Performance)
Message-ID: <69@abvax.icd.ab.com>
Date: Fri, 25-Sep-87 09:29:21 EDT
Article-I.D.: abvax.69
Posted: Fri Sep 25 09:29:21 1987
Date-Received: Sun, 27-Sep-87 10:38:19 EDT
References: <2903@phri.UUCP>
Organization: Allen-Bradley Company, Inc; Industrial Computer Division, Highland Heights, OH
Lines: 21
Xref: mnetor comp.arch:2375 comp.unix.wizards:4516 comp.os.misc:245

in article <2903@phri.UUCP>, roy@phri.UUCP (Roy Smith) says:
> Xref: abvax comp.arch:1448 comp.unix.wizards:2522 comp.os.misc:138
> dynamic loading, if you prefer) is the problem of backward compatability.


I would hope that any shared library system would give some ability
for each executable to link into specific revisions of each library
routine.

The author of the code will probably have to go and update the code
to make it work with the latest and greatest sometime.

BUT you can't get into the situation where whenever a library changes
all installed software has to be retested immediatly.


-- 
		Clive R. Charlwood @ Allen-Bradley Company
		Industrial Computer Division
		747 Alpha Drive, Highland Heights, OH   44143
		...!{decvax,masscomp,pyramid,cwruecmp}!abic!crc