Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!shelby!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Library function redefinition
Message-ID: <1396@toaster.SFSU.EDU>
Date: 4 Mar 91 09:06:55 GMT
References: <DBRENNER.91Mar3012022@sparta.weeg.uiowa.edu> <1389@toaster.SFSU.EDU> <DBRENNER.91Mar4014752@sparta.weeg.uiowa.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 13

What do you do about the case where procedures in the shared
library call other procedures in the shared library?  Should
they continue to reference their shared library versions?
Or yours?  If you opt for the former, you can no longer
statically link.  If you opt for the latter, you can break
library routines that you _didn't_ redefine (what works in
one software release might not in the next if the library
changes, etc.).

Refusing to link multiply-defined symbols keeps you out of
trouble.

					-=EPS=-