Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries
Message-ID: <6461@brl-smoke.ARPA>
Date: Wed, 23-Sep-87 14:39:29 EDT
Article-I.D.: brl-smok.6461
Posted: Wed Sep 23 14:39:29 1987
Date-Received: Sat, 26-Sep-87 03:49:16 EDT
References: <6886@eddie.MIT.EDU) <2501@xanth.UUCP> <2067@sfsup.UUCP> <2903@phri.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11
Xref: mnetor comp.arch:2314 comp.unix.wizards:4433 comp.os.misc:220

In article <2903@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>What do I do on a shared
>library system when scanf changes out from under me and breaks my program?

Obviously, you fix your program.  You need to do that anyway
the next time you recompile it (e.g. during routine maintenance).

This use of shared libraries depends on there being a stable
interface definition for the shared routines.  If your code
depends on anything not guaranteed by the interface definition,
then you were asking for trouble all along.