Newsgroups: comp.unix.internals
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Subject: Re: Shared Libraries YO!!!
Message-ID: <1991Jun27.081210.26026@Think.COM>
Sender: news@Think.COM
Reply-To: barmar@think.com
Organization: Thinking Machines Corporation, Cambridge MA, USA
References: <1991Jun10.154811.11965@infonode.ingr.com> <18370004@hpfcso.FC.HP.COM> <349@titccy.cc.titech.ac.jp>
Date: Thu, 27 Jun 91 08:12:10 GMT
Lines: 16

In article <349@titccy.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes:
>You can do bug fixes and performance enhancements at *every* release without
>losing transparency.

With static libraries, how do you incporporate bug fixes and performance
enhancements transparently?  You have to relink things to make them pick up
the improvements.  Commercial software is often distributed as prelinked
executables, without the original .o files, so you can't even relink it if
you want to.

New versions of shared libraries, however, are used automatically.
-- 
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar