Everyone here knows about what is Dynamic and static buddy
Yeah, I agree with you...
Static link method: comment #pragma (LIB, "test.lib"), the time of the static link, loading code will be used by the program to determine the dynamic code or code.
The link of the static library can be used for static link, and the dynamic link library can also be used to link the import library.
Dynamic link method: /GetProcessAddress () FreeLibrary () and LoadLibrary (), use this method to complete the dynamic link, but until the real call to the dynamic library code, loading program to calculate (the part of the code is called), and then wait until a certain time, the program will need to call another piece of code.
I personally believe that if you have multiple applications on the system to use the library, it will be compiled into a dynamic library, so that although the load is relatively slow, but more tasks will be saved memory; if your system is only one to two applications using the library, and the use of less than API, it is compiled into a static library, the general static library can also be compiled, so that the application may be relatively large, but the speed will be greatly improved.
Some of the personal experience, the inadequacies, welcome to!
