Peter Slegg schreef op 12/19/14, 9:29 PM:
Then each would load it's own copy of the libs so there would be A, B, B, C and C in memory. Each app can call it's own copy just like static linked versions.
You seem to forget that most programs only need parts of libraries. It could be possible that your programs use different parts of each library. The memory inefficiency of static linking depends on the size of the part of the library used by all programs. Static linking might not be as inefficient as most people think. Besides that its concept is rather uncomplicated and a lot more safe than dynamic linking with suspicious libraries each time a program is run. Just a few cents. -- Groeten; Regards. Henk Robbers. http://members.chello.nl/h.robbers Interactive disassembler: Digger; http://digger.atari.org A Home Cooked C compiler: AHCC; http://ahcc.atari.org