Differences between version 7 and previous revision of SharedLibrary.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 7 | Last edited on Monday, October 4, 2004 3:48:58 am | by StuartYeates | Revert |
| Older page: | version 6 | Last edited on Sunday, October 3, 2004 3:00:32 pm | by PerryLorier | Revert |
@@ -1,5 +1,5 @@
-A SharedLibrary contain
subroutines that can be linked to a BinaryExecutable at RunTime. This allows for sharing code between applications, which has a number of advantages:
+A SharedLibrary contains
subroutines that can be linked to a BinaryExecutable at RunTime. This allows for sharing code between applications, which has a number of advantages:
* It saves on disk space, since functions common to many programs don't need to exist in identical copies in each of their binaries.
* It saves on memory for the same reason -- you only need a single copy of the SharedLibrary in memory. This also means that the memory footprint columns in ps(1) never add up correctly.
* Fixing a bug in the shared code automatically fixes that bug for all programs that use the library, without actually having to touch these programs.
