When to write Dynamic Linking Libraries

Question

0.00/5 (No votes)

See more:

Hi,
Can you please let me know as to why one should actually start writing Dynamic Linking Libraries.

How about the performance?

:)

Posted 12-Aug-12 9:29am

AshakiranBhatter

Add a Solution

2 solutions

Solution 1

Becouse with a dll you can load the function into memory when you need it, and kick it out of memory when not needed.

Posted 12-Aug-12 9:31am

Kenneth Haugland

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Philip Stuyck · Accepted Answer · 2012-08-12T09:36:00

When the functionality you put in your dll is going to be used by more than one module.
You could put it in a library but then it will be linked in your assembly/executable and eventually the same code is contained in multiple places. (multiple executables)
On top of this, if the code changes but the interface does not, you can change a dll without having to replace all the code that makes use of the dll.
Some libraries are very smart and offer you the possibility to choose between a dll and a lib. For instance MFC offers this choice. If you link, you get a bigger executable, containing the part of mfc you actually use, if you use a dll, well your executable will be smaller.
Code that is reusable should be put either in a library or in a dll, or you simply share the code all the time and compile and link it allways.