There's an order by which exe's look for libraries. It will use the first one it finds, I believe CPallini gave you a link that specifies the search order. You can use tools such as Dependency Walker[^] to see what dll specifically is getting loaded by an exe if you're not sure which one it's loading. It is customary that shared dll's are placed in a location where any program that wants to use it has access to it, of course, this will require admin privilidges for your installer (assuming you place the dll copy in a system folder).

Or VARIANT, if it's Win32.

dynamic_cast must be useful in parent child relation of classes. It helps to determine object type in a hierarchy. i.e - class Base{ }; class Derived1:public Base{ void der1Fun(){} }; class Derived2:public Base{ }; int main() { Base *bPtr = new derived1(); //now we want to call a derived1 function let der1Fun() Derived1* dPtr = 0; if( dPtr = dynamic_cast(dPtr) ){ dPtr->der1Fun() } else{ //Display the object is not of derived1 type } return 0; } I think this is why we need dynamic_cast.

I agree with you! In general, two cases are identical!

Oh, now I see. You are looking for an example of 'idiosyncrasy of integer promotions' (see, for instance, , however shaktikanta wrote: 0 is by default unsigned is a wrong assumption. It is signed, by default. You have to write: #include <stdio.h> int main() { int k; if ( 0u < -1) { k=5; } else { k=10; } printf("%d\n", k); return 0; } Veni, vidi, vici.