|
|
Orchid XP v7 wrote:
> How does this stuff work with Windoze? (Or Linux, for that matter...)
Dynamic link libraries (DLLs) two ways to get to them, either through
the linker, or through dynamic loading through calls to LoadLibrary and
GetProcAddress. The easiest way is using the linker, of course, provided
you have the header & library files (which you should for any windows
compiler available). The DLL loader does all of the procedure address
fix-ups, if a DLL is loaded into its preferred address space (i.e. no
other DLL is occupying the address space it requests), then loading is
much quicker since all of the pointers in the function table are
correct. Alternatively, some functions, such as those in the DirectX and
Shell libraries use COM, in which instances of classes are loaded with
vtables pointed to the correct functions. DirectX (and Shell, I think)
export non-COM functions for creation of the COM class instances.
* This is simplified and largely from memory, so take it for what its
worth (not much). This is also the case for Win32, Win16 may be
different, Win64 should be similar, though.
Post a reply to this message
|
|