Introduction
Efficient and appropriate use of header files requires a few tricks. If you simply define a set of functions, everything works fine. No problems. If the file is included more than once because of a complex #include chain, you get redundant declarations. Most compilers, including the Microsoft C / C compilers, simply ignore these redundant function and variable declarations. However, if there are any class, typedef, struct, or some other declarations, the compiler will complain bitterly if they are seen twice, claiming they are duplication declarations. It does not choose to see if the structures actually are identical. So there is an idiom to avoid duplication declarations, which is to put the entire contents of the header file in an #ifndef, skipping the body if a symbol defined within THE BODY IS ALREADY WELL for short files, but is a performance dispiled, exad. for standard headfall, precompiled headers work well in eliminating this problem, but it is harder to justify putting your own headers into a precompiled header file since the effects of a simple change result in a massive recompilation (stdafx.h has to be recompiled). Microsoft has added a # Pragma That Means The Header File Is Read Only. All of this is shown in detail below.
DLL Headers: Additional Complexity
When constructing a DLL, you need a header file to interface to it. However, the obvious solutions do not work as expected. For example, if you declare a function in a fashion so as to export it, you need to add __declspec (dllexport ) to its declaration, and if you do not want name mangling, particularly important if you expect to use the DLL with straight C code as well as C , you need to define it in the .cpp file asextern "C" __declspec (dllexport ) Function-HEADER
{
// ... Whatver
}
The Problem with this approach is there. The obvious solution.............
The First Wrong Approach
THE FIRST Attempt You Might Make Is To Declare, In The .h File
Extern "C" function-prototype; // incorrect
This does not work because the compiler will complain that the prototype is incompatible with the declaration. What causes this is the prototype lacks the __declspec (dllexport) declaration. So, you say, I'll just add that in. So you get
Extern "c" __declspec (dllexport) function-prototype; // incorrect
This does not work for a different reason. Although you will no longer get a warning when you compile the DLL, you will get a warning when you compile the application, because the declaration __declspec (dllexport) is incompatible with the use of the function Call.
The Second Wrong Approach
At this point a couple workarounds present themselves. The first one you might consider is to use two header files, one of which has the __declspec (dllexport), and the other of which does not. This is a Bad Idea. The reason is that you lose the consistency checking you would get if you include the same header file into both the DLL compilation and the client compilation. For example, if you change the function to have a different parameter type, the compiler will complain unless you change the DLL's header file prototypes to correspond. But in this case, the DLL header file is completely useless, and might as well not exist, because there is a completely separate header file for the client. It remains uncorrected, and there is no cross-check against the Actual Module. You Lose.a Workable But Inconvenient Approach
At this point, you could remove the __declspec (dllexport) declarations entirely. This means your one-and-only header file will be consistent with the source, but, whoops, the symbols are not exported. To get around this, you can add either the / exports:. function command line switch to the linker command line, or use a .def file and add the function name to the EXPORTS section This is a valid, correct solution, and it works, but you will find that it quickly becomes inconvenient, because you have to remember to add the function name declaration to the / exports switch or add the name to the .def file. Anyone who did DLLs or Windows programming in Win16 in the days before the __export keyword was added to that language will remember how bad this was. Those of you who did not, take our word for it, it was a real royal pain to deal with this. So I'm disinclined to use this solution unless there are other compelling reasons, which there rarely Are.The Ultimate Header File
This is a model which I have cut-and-pasted many times for every DLL I've built in recent years. I've added some comments to help explain and show visually what is going on, and you will probably want to remove these BEFORE ACTUALLY IT.
The uniquename name is something of your own choice. It could be a simple text string, e.g., _DEFINED_MYDLL_HEADER, or you could use GUIDGEN to create a GUID. If you use GUIDGEN, create a "Registry Entry" format, which is
{EBE7C480-A601-11D4-BC36-006067709674}
Remove the {} s Andrew the Hyphens with underscores. This Would Give You a Symbol Like
_DEfined_ebe7c480_a601_11d4_bc36_006067709674
Which Guarantees That You Will Never, Ever Have a conflict with any other header file.
#ifndef _Defined_uniqueheadername // --------------- 1 -------------- # define _defined_uniqueheadername // ---------------- ------- 1 ---------------
// |
#iF _MSC_VER> 1000 / / ------------------------------- |
#pragma overce // | | |
#ENDIF / / - ------------------------------------------ |
// |
#ifdef __cplusplus // --------------- 3 --------------- |
Extern "C" {// | | |
#ENDIF / / __CPLUSPLUS / / ------------ 3 --------------- |
// |
#ifdef _Compiling_uniqueHeadername // ----------- 4 ----------- |
#define libspec __declspec (dllexport) // | |
#ELSE / / | | | |
#define libspec __declspec (dllimport) / / | | |
#ENDIF // _Compiling_UniqueHeadername // -------- 4 ----------- |
// | |
Libspec LinkageType ResultType Name (Parameters); // | |
// ... more declarations as needed // | |
#undef libspec // ----------------------------------------- |
// |
#ifDef __cplusplus // ------------------------------- |
} // | | |
#ENDIF / / __CPLUSPLUS / / --------------- 5 --------------- |
#ENDIF / / _DEfined_uniqueheadername // ---------------- 1 ------------
The Explanation of the "Contour Lines" is as five
If the header file is actually processed, this is the traditional C idiom to keep it from being processed twice. The first time the file is included, the symbol _DEFINED_uniqueheadername is not defined, so the file is processed. The first thing it does is declare that symbol, so that in subsequent inclusions, the entire body of the file is skipped. This is a #pragma which is defined only for C compilers version 10.00 and later (note that the C compiler version and the VC version are not related numbers) . If this #pragma is implemented, the inclusion of this file in a compilation creates an entry in an "included files table" for that compilation. Subsequent attempts to include this file in the same compilation first check this table, and if the filename is the same, the compiler does not even bother to open the file. However, you can not eliminate the contour 1 test, because this #pragma, for reasons best known only to its implementor, is case sensitive in the file name, even Though the file name of the underlying operating system is case insensitive. It seems utterly silly that we should have two discrete behaviors, but since when has rationality and common sense affected what some programmers do? This contour is required to make the header file compatible with both C and C . It assumes that you want C compatibility, and therefore that the function names should not have C "name mangling" applied. The downside of this is that you lose the ability to overload functions based on parameter types. If you are doing a C - Only DLL, You Would Not Use this Contour, And you Would Also Eliminate Contour 5. The __cplusplus Symbol IS Defined for A C
compilation but undefined for a C compilation. This is a funny contour. The # if / # else / # endif contour decides which form of __declspec to use for the declaration. The scope of the effect of this contour actually projects beyond the conditional and extends . to the #undef, during which the symbol LIBSPEC is defined Strictly speaking, you do not need to do the __declspec (dllimport); you could just define LIBSPEC as an empty macro However, declaring __declspec (dllimport) does same one or two. instructions on the linkage when it is finally resolved. Since, using this method, it costs nothing to add this slight efficiency, why not? Note that contour 4 is not needed for non-DLL files. This is the matching close brace to the structure created in contour 3. If you are doing a C - only DLL, you would eliminate this as well as contour 3.Now, in the DLL itself, you have to do one thing: you must declare the _COMPILING_uniquename symbol before the #include. After That, You Simply Declare The Functio N as shown.
#include "stdafx.h" // USUALLY
#define _Compiling_uniquename
#include "mydll.h"
Extern "C" __Declspec (dllexport) LinkageType ResultType Name (parameters)
{
// ... Whatver
}
And You Will NOT GET Any Compiler Conflicts. This Will Use The Same Header File for Both The DLL AND Client, And All The Right Things Will Happen.
