Whats the Difference between Static And Dynamic PDFs?

What's the difference between static and dynamic PDFs?

Before moving on to the difference, lets see the linking process in brief. Why linker ? When you write some C code (or any other language), it is stored in .c format. #include int main { printf("quora"); return 0; } Now this program goes through the compilation phase in which this source code is converted to machine language instructions. These are the object files stored as .o or .obj format. If we have 2 separate files, we will have 2 separate obj files. These files are just the translation of your program, to run these programs we have to generate executable which the OS can actually run. For this purpose, we use linker. Now linker creates single executable file out of many object files. Now in our C program we used main function, but where is its definition. The scope of compiler is limited to one file only so it doesn’t look for references which may have been declared and defined in other files. Linker search multiple files for this “main ” function definition and links them. Now coming to your question. Static vs Dynamic linking. In static linking, all the library modules are copied to the final executable image. When the program is loaded, OS places only a single file to the memory which contain both the source code and the referencing libraries. Whereas in dynamic linking only the names of external or shared libraries is placed into the memory. Dynamic linking lets many programs use single copy of executable module. Static linking is done by the linkers in the final step of the compilation whereas the dynamic linking is done at run time by the OS. Statically linked files consume more disk and memory as all the modules are already linked. But in Dynamic linking, only one copy of the reference module is stored which is used by many programs thereby saving memory and disk space. In Static linking, if external source program is changed then t have to be recompiled and relinked. But in case of dynamic linking only a single module needs to be updated and recompiled. Statically linked programs are faster than their dynamic counterpart. Since the statically linked file contains every package and module, no compatibility issues occur. Whereas in dynamic linking, since the library files are separately stored there may be compatibility issues ( say one library file is compiled by new version of compiler). Statically linked programs always take constant load time whereas the time is variable in dynamically linked programs.