Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uwm.edu!linac!att!att!drutx!ldg@drywit.ATT.COM
From: ldg@drywit.ATT.COM (XGPB30000-GibbonsD(DRR6702)262)
Newsgroups: comp.unix.wizards
Subject: Re: Shared Libraries: Unique to Suns??
Message-ID: <7915@drutx.ATT.COM>
Date: 22 Mar 91 17:35:55 GMT
References: <1991Mar21.035115.21842@NCoast.ORG>
Sender: news@drutx.ATT.COM
Reply-To: ldg@drywit.ATT.COM
Lines: 27

From article <1991Mar21.035115.21842@NCoast.ORG>, by allbery@NCoast.ORG (Brandon S. Allbery KB8JRR):
> 
> System V has shared libraries, but you have to design your libraries for them
> --- they are *not* trivial to set up.  I know little about the SunOS
> implementation, but it looks rather easier to use.
> 
> (Has this been addressed in SVR4?)
> 
> ++Brandon
> -- 

SVR4 has indeed addressed this question. The implementation of shared
libraries, or "shared objects" in SVR4 is based upon the Sun design.
The SVR4 shared object is easier to make and use than its SVR3 counterpart,
and the performance issues are  similar. A good treatment on this
subject can be found in the "UNIX System V Programmer's Guide: ANSI C
and Programming Support Tools. This book is shipped with the AT&T
ANSI C compiler software. Also, see the "System V Application Binary
Interface" - ISBN 0-13-877598-2.



--
--------------------------------------------------------------------------------
-- Doug Gibbons			| ldg@druhi.ATT.COM or att!druhi!ldg
-- AT&T Bell Laboratories 
-- Denver CO