Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!uunet!hsi!stpstn!lerman
From: lerman@stpstn.UUCP (Ken Lerman)
Newsgroups: comp.unix.wizards
Subject: Re: Shared libraries (was Re: Window system bashing (was Re: X11 bashing))
Message-ID: <6783@stpstn.UUCP>
Date: 17 Apr 91 11:42:13 GMT
References: <26550@adm.brl.mil> <97@titccy.cc.titech.ac.jp> <1991Apr15.173955.7909@athena.mit.edu> <1991Apr15.224311.3950@ida.liu.se>
Reply-To: lerman@stpstn.UUCP (Ken Lerman)
Organization: The Stepstone Corporation, Sandy Hook, CT 06482
Lines: 26

In article <1991Apr15.224311.3950@ida.liu.se> d89peter@odalix.ida.liu.se (Peter Eriksson) writes:
>
>I would even go as far as saying that they mostly have positive side-effects.
>That way bug-fixes in the libraries can be introduced and automatically be
>in effect in all the programs that use those libraries. No need to recompile
>all zillions small and big programs.
>
>--
>Peter Eriksson                                              pen@lysator.liu.se
>Lysator Computer Club                             ...!uunet!lysator.liu.se!pen
>University of Linkoping, Sweden                               Support the LPF!

Way to go...

So I spend weeks trying to track down some bug in one of your
libraries.  Then, since I don't have the source code, I come up with
some ghastly workaround so I can ship my product.

Two weeks after I ship the release to two thousand customers, you
release a new version of your library.

And my code stops working.

A bug fix IS a change in functionality.

Ken