home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.apollo
- Path: sparky!uunet!caen!sdd.hp.com!apollo.hp.com!netnews
- From: ganek@apollo.hp.com (Dan Ganek)
- Subject: Re: Making /lib/xmlib1.1 a global library in SR10.4
- Sender: usenet@apollo.hp.com (Usenet News)
- Message-ID: <BxoDqw.ss@apollo.hp.com>
- Date: Fri, 13 Nov 1992 22:13:43 GMT
- References: <1992Nov7.033430.26974@nrtpa038.bnr.ca> <1992Nov13.215059.1429@hpcvusn.cv.hp.com>
- Nntp-Posting-Host: menage_a_trois.ch.apollo.hp.com
- Organization: Hewlett-Packard Corporation, Chelmsford, MA
- Lines: 36
-
- In article <1992Nov13.215059.1429@hpcvusn.cv.hp.com> tomg@hpcvusc (Thomas J. Gilg) writes:
- >Bill Gutknecht (bag@node_1f11c.bnr.ca) wrote:
- >> I'd like to make the library globaly loaded in an effort to save memory
- >> and help performance .....
- >>
- >> Anyhow, I entered the following two lines into /etc/sys.conf
- >>
- >> lib xtlib.r4, global, optional # Needed to resolve globals in xmlib1.1
- >> lib xmlib1.1, global, optional
- >
- >Under Domain/OS, the load order of shared libraries is very critical. As
- >an example, consider the sequence of events when running vuewm:
- >
- [inlibing info deleted]>
- >
- >A key question for which I don't have an answer is whether shared libraries
- >in /etc/sys.conf will have their main() routines executed if they have one.
- >In the X/Motif libraries, it is absolutly critical that the main() routines
- >in the libraries get executed so that things like vendorShell can be
- >properly initialized.
- >
- >
- >Thomas Gilg
- >tomg@cv.hp.com
- >
-
- Bill, making a library global doesn't save memory (real or virtual)
- over inlibing. It doesn't help performance much either.
-
- Tom, the main routine of a global library is executed for EVERY process that
- is started whether it uses it or not. For that reason, global libs should NOT
- have a main() unless it is absolutely necessary.
-
- (At least that's what I rememebr from the good old days)
-
- /dan
-