Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!rick From: rick@uunet.UU.NET (Rick Adams) Newsgroups: comp.sys.pyramid Subject: Re: Pyramid Support of Shared Libraries Summary: plus and minus Message-ID: <63323@uunet.UU.NET> Date: 11 Aug 89 15:28:39 GMT References: <17347@bellcore.bellcore.com> <79957@pyramid.pyramid.com> <17350@bellcore.bellcore.com> Organization: UUNET Communications Services, Falls Church, VA Lines: 12 > Once shared libraries are available, it would be possible to make fixes > to standard libraries without touching the application binaries. This is one > of two main benefits of shared libraries. Note that this also raises the problem of breaking existing binaries that depend on the 'old' behavior of the library routine. You have to be very careful about fixing shared library modules if you dont expect to break something that was already working. Version numbers are a start, but then you dont get the automatic update that you mentioned