News for hackers. Stuff that matters.
Re:32-bit x86 Position Independent Code – It's That Bad by kazinator on Wednesday April 15, 2015 @10:36AM (#9381221)
Windows DLL's don't have features such as the executable overriding symbols in the attached library.

In fact, if you call LoadLibrary at runtime, there is no symbol resolution; you have to look up symbols yourself using GetProcAddress.

Under dlopen, symbol resolution takes place; it can change the destinations of function calls.

Re:32-bit x86 Position Independent Code – It's That Bad by userbinator on Wednesday April 15, 2015 @10:59AM (#9381373)
Under dlopen, symbol resolution takes place; it can change the destinations of function calls.

I'm probably a bit biased since I'm rather used to Windows' explicit import-export system, but having function calls change just because a library was loaded sounds like an opportunity for some extremely confusing bugs.