Shared objects are libraries that can be used by multiple programs (or
multiple
versions of the same program.
Take for example the following 4 programs:
A Requires libs 1 3 4 8
B Requires libs 2 3 4 5 6 7
C A copy of B
D Requires libs 1 3 6
If we DON'T have shared libs, then we would have the following:
1346234567234567136 as memory segments.
With shared libs, we can do this:
13482567
which means SIGNIFICANTLY less memory used for the libs. That means
less page swapping->FASTER and more efficient.... a win-win situation.
This is a gross simplification, but it should show why shared libs
are far preferred from non-shared libs.
Bill Ward
-----Original Message-----
From: David Krings [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 29, 2000 10:33 AM
To: [EMAIL PROTECTED]
Cc: recipient.list.not.shown; @nswcphdn.navy.mil
Subject: Re: [OT]: "so" differences between libs
Hi !
Thank you very much for your reply....but what is a shared object ?
So a
non-so version isn't a shared object and therefore is different than the
so-version ? If there is no difference then i'd get any version and just
softlink so that the name can be found.
Thank you for any hints,
Greez
Dave
>the .so means shared object, normally.
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
