Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-unix!husc6!linus!philabs!pwa-b!mmintl!franka
From: franka@mmintl.UUCP
Newsgroups: comp.arch,comp.lang.c
Subject: Re: String Handling and run-time libraries
Message-ID: <2093@mmintl.UUCP>
Date: Mon, 6-Apr-87 19:05:13 EST
Article-I.D.: mmintl.2093
Posted: Mon Apr  6 19:05:13 1987
Date-Received: Wed, 15-Apr-87 04:12:22 EST
References: <15292@amdcad.UUCP> <978@ames.UUCP> <15694@sun.uucp> <6042@mimsy.UUCP> <287@pembina.alberta.UUCP> <1417@castor.usc.edu>
Reply-To: franka@mmintl.UUCP (Frank Adams)
Organization: Multimate International, E. Hartford, CT
Lines: 13
Xref: utgpu comp.arch:863 comp.lang.c:1600

In article <1417@castor.usc.edu> blarson@castor.usc.edu.UUCP (Bob Larson) writes:
>In article <287@pembina.alberta.UUCP> bjorn@alberta.UUCP (Bjorn R. Bjornsson) writes:
>>Assuming a vectored entry point interface to the library,
>
>This isn't the only, or nessisarily best, way to implement shared
>libraries.  Primos implements shared libraries via faulted links.

The major problem with this is programs which throw function pointers
around, instead of just calling the routines.  If you aren't careful, you
wind up faulting *every* call in some contexts.

Frank Adams                           ihnp4!philabs!pwa-b!mmintl!franka
Ashton-Tate          52 Oakland Ave North         E. Hartford, CT 06108