In C++, I have some header files such as: Base.h, and some classes using Base.h:
//OtherBase1.h
#include "Base.h"
class OtherBase1{
// something goes here
};
//OtherBase2.h
#include "Base.h"
class OtherBase2{
// something goes here
};
And in main.cpp, I can only use one of those two OtherBase classes because of duplicate header. If I want to use both classes, in OtherBase2.h I have to #include "OtherBase1.h" instead of #include "Base.h". Sometimes, I just want to use OtherBase2.h and not OtherBase1.h, so I think it’s really weird to include OtherBase1.h in OtherBase2.h. What do I do to avoid this situation and what’s the best practice for including header file?
You should be using include guards in
Base.h.An example:
This will prevent multiple-inclusion of
Base.h, and you can use bothOtherBaseheaders. TheOtherBaseheaders could also use include guards.The constants themselves can also be useful for the conditional compilation of code based on the availability of the API defined in a certain header.
Alternative:
#pragma onceNote that
#pragma oncecan be used to accomplish the same thing, without some of the problems associated with user-created#defineconstants, e.g. name-collisions, and the minor annoyances of occasionally typing#ifdefinstead of#ifndef, or neglecting to close the condition.#pragma onceis usually available but include guards are always available. In fact you’ll often see code of the form: