Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!convex!darwin.sura.net!news-feed-1.peachnet.edu!umn.edu!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: Shared libraries Message-ID: <hastyC78FLw.4H2@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <PC123.93May14232156@bootes.cus.cam.ac.uk> <1tau5kINNq52@scarecrow.mke.ab.com> Date: Tue, 18 May 1993 17:08:19 GMT Lines: 25 In article <1tau5kINNq52@scarecrow.mke.ab.com> tdphette@mke.ab.com (Thad Phetteplace x4461) writes: >pc123@cus.cam.ac.uk (Pete Chown) writes: >: I have put a prototype shared library package in the /tmp directory of >: src.doc.ic.ac.uk. If it has been wiped from there, you will be able >: to get it from dale.chu.cam.ac.uk, in /pub, but this machine is not >: always switched on (afternoons and evenings UK time only). > >[ stuff deleted ...] > >One quick question. Does your implementation used static or dynamic >entry points? One thing I look for in a shared library is not having >to recompile all my apps when the library changes slightly. > He uses a jump table. so relinking with the new shared library in most cases is not needed. this is explained in the documentation included in his package :-) Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/incoming