Talk:Library (computer science)
|
|
| Contents |
Partial list of topics to fill in
I moved this from the article, since it really belogs here:
- Application Programming Interface
- relationships among linkers, loaders, dynamically linked library, statically linked library, application binary interface
- Common styles of library organization (GUI toolkits, data structure/collection frameworks, I/O libraries, functional programming combinators, metaprogramming protocols, etc.)
- Perhaps a section on Prebinding?
—Frecklefoot 18:36, 18 Sep 2003 (UTC)
I merged many library-related articles to here. The article looks too long but there is a lot of overlaps. The article can be compact. -- Taku 00:36, 22 Sep 2003 (UTC)
Hmm while checking "what links here" from metaprogramming I came across this talk. Would someone care to add information on what a metaprogramming protocol might be? -- Anon
- Protocol in this context means method or workflow. One metaprogramming protocol is direct metaprogramming where the programmer writes a program-writing program. A second protocol might be genetic programming where the programmer writes some form of specification and the computer tries to create a program to fulfill it. A third protocol might be indirect metaprogramming via a metaprogramming tool such as Bison where the programmer writes a specification which the tool uses to generate a program. This third protocol is probably what is meant above. -- Derek Ross
Are static linking and dynamic linking supposed to be subtopics of library linking? If so the hierarchy is all skew. --BozMo|talk 15:17, 16 Aug 2004 (UTC)
.dll
Please consider the following: If someone arrives at Library (computer science) via a redirect from .dll (which, if I'm not mistaken, is the extension of a file name) or DLL they should at least be presented with some sort of explanation as to what .dll is/means at the beginning of the article. Could someone add a note? <KF> 19:08, Nov 16, 2004 (UTC)
- I have changed the redirect from .dll and the link on the DLL disambiguation page to jump to the correct subsection so that a proper explanation is presented. Nixdorf 06:13, 2005 Apr 12 (UTC)
A question
"Dynamic linking systems place the majority of the linker code in the underlying operating system, in which case it is known as a loader."
What does "it" refer to in the sentence above?
UNIX PATH envariable is not used to lookup dynamic libraries
In the section about Dynamic Linking you say:
Unix-based systems use a PATH variable of "places to look", which tends to be robust as the PATH rarely changes.
It sounds like you are reffering to the shell PATH variable. As far as I'm aware, none of the common UNIX variants uses the PATH environment variable to lookup shared objects (aka Dynamic Libraries). Instead there are: 1. Pre-defined, system-wide paths configured in files (e.g. /etc/ld.so.conf on Linux. See ldconfig(8) for more) 2. Possibly other environment variables to override/add to the directories in (1) (e.g. LD_LIBRARY_PATH, LD_PRELOAD and others on Linux).
The only resemblance to PATH in the above is that the environment variables, if defined, are usually in the format of the standard PATH variable used by the bourne-shell to lookup programs (i.e. directory names separated by commas).
I remember seeing somewere a list of the variations on this theme (of LD_LIBRARY_PATH equivalents on "exotiq" systems like HPUX and AIX) but can't find it right now, maybe a good place to begin digging is GNU libtool).
I'm adding this here because I'm not sure how to edit the article itself.
Thanks. Penedo 02:35, 28 Apr 2005 (UTC)