What (if any) are the pitfalls of leaving unused dynamically loaded libs linked into a C++ application build?
<p>Question says it all really. This is more for my own curiosity to see if anyone knows of a particular reason why this should be avoided!</p>

<p>The only thought I have had is that perhaps, even if no library functions are called, the compiler will still generate loading code and load the library even though it will not be used. I'm guessing here, would be interested to know what the implications actually are!</p>

<p>Thanks!</p>