Jump thunk table?
1 reply to this topic
Members - Reputation: 1375
Posted 19 September 2011 - 01:36 AM
It's just a table of jumps to code which actually does the work. The point being that code outside the module can just call to well-known entry points. Those entry points are jumps to the real routines. The real routines can move around in different versions of the library and the user code doesn't need to be relinked.