home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!mcsun!fuug!funic!nntp.hut.fi!vipunen.hut.fi!sakaria
- From: sakaria@vipunen.hut.fi (Sakari Aaltonen)
- Subject: Jump Tables: A Mystery
- Message-ID: <1992Aug15.085244.10732@nntp.hut.fi>
- Sender: usenet@nntp.hut.fi (Usenet pseudouser id)
- Nntp-Posting-Host: vipunen.hut.fi
- Reply-To: sakaria@vipunen.hut.fi (Sakari Aaltonen)
- Organization: Helsinki University of Technology
- Date: Sat, 15 Aug 1992 08:52:44 GMT
- Lines: 29
-
-
- Several people responded to my recent whining about shared libraries
- by mentioning "jump tables".
-
- Jump tables?
-
- Is there a book or an article that explains the structure of shared
- libraries and of programs using them? I, too, would like to understand
- jump tables. I just can't find anything on them in Tanenbaum.
-
- My impression now is that shared libraries are something like MS-Windows
- dynamic link libraries. "Dynamic" seems a good description, as a matter
- of fact - code that is loaded into memory dynamically, at runtime.
-
- However, I think you can change MS-Windows DLL's as often as you like
- without recompiling or relinking the programs that use the libraries.
- You just have to keep the name of the DLL and the indexes of the functions
- therein the same, because the calling programs refer to the functions by
- library name (LINUX.DLL, say) and index (96, say). I don't know whether the
- name of the function matters.
-
- Why can't shared libraries be like that?
-
-
- --
- -----------------------------------------------------------------------------
- Sakari Aaltonen Helsinki University of Technology
- Email: sakaria@vipunen.hut.fi
- --- You can't keep a Finn down without him getting all red in the face ----
-