What's the difference between static and a dynamic call with respect to their load module creation?

Showing Answers 1 - 2 of 2 Answers

if Prog A calls Prog B statically then they have a single load module say LOAD A

if Prog A calls Prog B dynamically then Prog A has a load module say LOAD A & Prog B has a seperate Load module say LOAD B.

  Was this answer useful?  Yes

lfrank

  • Jan 8th, 2008
 

A statically linked subroutine becomes part of the load module at link-edit time. At execution time, the routine is present when the module is brought into memory from the load library.

A dynamically linked subroutine only establishes "link points" during link-edit. At execution time, the routine is not present when the module is brought into memory but is 'dynamically' loaded when it is called.

The static approach is more efficient but if the subroutine is changed, every program calling it needs to be relinked. With the dynamic approach, relinking is unnecessary since the latest module is loaded from the load library.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.