Skip to main content

What is a DLL ? What are different dll's supported in VC++ ? Explain different types of dll's.

A DLL is a dynamic link library. It provide a way of sharing common code at runtime . Any appication( exe) can load a dll in to memory at runtime, retrieving the address of the fuctions to be called / accessing resources or variables. client can use the functions, variable or resources and unloads the dll from memory.

One can load the dlls either statically or dynamically.

Dynamically loading -

HANDLE h = LoadLibrary("MyDll.dll"); // load dll

typedef FUNPTR (void) (*funcPtr ) (); // create a fuction pointer with matching signature // with that of exported function from dll.

FUNPTR show = GetProcAddress( h, "Show"); // Get function address
show(); // Call the fuction
FreeLibrary(h); // unload dll from memory

Statically loading:

Include the .h file and specify .lib file to the linker for specified dll. User can access the dll content ( Exported fuctions, resources, variables) at compile time itself.

Regular, Extension and pure Win32 DLL (without MFC)

Regular DLL

Regular DLL's can export only functions, variables or resources. These can be loaded by any Win32 environment (e.g. VB 5) Regular DLLs are generally larger in size. When you build a regular DLL, you may choose a static link (in this case MFC library code is copied to your DLL) and dynamic (in this case you would need MFC DLLs to be presented on the target machine)

Extension DLL

Along with functions, variables and resources Extension DLL's can export Classes as well. It supports a C++ interface, i.e. can export whole C++ classes and the client may construct objects from them. Extension DLL dynamically links to MFC DLLs (those which name starts with MFC??.DLL) Extension DLL is usually small (simple extension DLL might be around 10K)

Pure Win32 DLL

This is simple dll, it does not use any MFC classes.

Labels:

Comments

Post a Comment

Popular posts from this blog

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives ...
17 comments
Read more

Function name mangling for C++ and Java

G++ internals - Mangling Both C++ and Jave provide overloaded function and methods, which are methods with the same types but different parameter lists. Selecting the correct version is done at compile time. Though the overloaded functions have the same name in the source code, they need to be translated into different assembler-level names, since typical assemblers and linkers cannot handle overloading. This process of encoding the parameter types with the method name into a unique name is called name mangling . The inverse process is called demangling . It is convenient that C++ and Java use compatible mangling schemes, since the makes life easier for tools such as gdb, and it eases integration between C++ and Java. Note there is also a standard "Jave Native Interface" (JNI) which implements a different calling convention, and uses a different mangling scheme. The JNI is a rather abstract ABI so Java can call methods written in C or C++; we are concerned he...
5 comments
Read more