Home/ Questions/Q 1060003
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T18:15:34+00:00

How do you solve created by including a header file with the same name

  • 0

How do you solve created by including a header file with the same name as another header file already indirectly included as a result of another include?

For instance:

// src/blah/a.hpp
#ifndef A_HPP
#define A_HPP

namspace blah
{

class A
{
}

}

#endif

// src/blah/b.hpp
#ifndef B_HPP
#define B_HPP

#includes "a.hpp"

namspace blah
{

class B
{
}

}

#endif

// src/foo/a.hpp
#ifndef A_HPP
#define A_HPP

namspace foo
{

class A
{
}

}

#endif

// src/foo/c.hpp
#ifndef C_HPP
#define C_HPP

#includes "../b.hpp"
#includes "a.hpp"       // won't be included due to multiple inclusion prevention

namspace foo
{

class C
{
}

}

#endif

In the last header file, a.hpp won’t be included because of the multiple inclusion preprocessor guards. Really, this should be okay though since the classes are in different namespaces. I realize that the easy way is to just change the name of foo/a.hpp or to just give it a fake name in the multiple inclusion guard. Is there a better way?

EDIT
I understand that you can solve this problem by using a more descriptive name in the #define and #ifndef directives (e.g. FOO_A_HPP and BLAH_A_HPP), but I want to know if that is the recommended or best way. Would some people recommend using a different file name as a better solution or does it not really matter? Would you recommend using the convention:

<NAMESPACE>_<CLASS>_HPP

instead of 

<CLASS>_HPP

to give a better chance of avoiding these problems in general?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You solve this, simply, by not using the same #define at the top …

    It would be better to use BLAH_A_HPP and FOO_A_HPP etc so that the #define also includes the namespace name.

    Edit: Well personally I recommend doing the following:

    1) Don’t name headers the same (ie use different file name … this doesn’t always help) and use different #define names..
    2) Don’t name classes the same thing. Put 1 class per header and name the header after the class
    3) If they are differentiated by a namespace use that namespace in the file name AND #define
    4) Add an ID to you #define that is unique to you (I could use GOZ for example)
    5) Make use of #pragma once. Its useful for the compilers that ise it.

    Its all a matter of taste though. Choose a scheme that works for you and stick with it. There is no right or wrong. As long as it works and is consistent.

    • 0