Compilers and assemblers generate object code from source files. Linking object files allows them to execute. Compilers can produce executables without linking. The latter approach's drawbacks?

Implement a Python script that generates a memory leak. One simple way to identify a memory leak is to look at the number of objects that are tracked by the garbage collector: if the final number of objects is bigger than the initial number (i.e. process started) then you may have a leak. Python script screenshot of the output

Compilers and Assemblers build object code files by translating each source file one at a time. As a result, running the object files requires linking them together first. However, it is theoretically feasible to bypass the linking stage and simply build the final executable file from the compilers. What would be the drawbacks of the second option?

What is the difference between dynamic and static libraries? A. Dynamic libraries are linked when executable libraries are added to memory, and static libraries are inked alter the program is placed in the memory B. Dynamic libraries are much larger than static libraries because external programs are built in the executable file that is added to memory C. Static libraries are linked when executable libraries are added to memory, and dynamic libraries are linked after the program is placed in the memory D. Static libraries can be linked to any program at run time however, the program has to be loaded for the dynamic library code to be used