Home/ Questions/Q 156527
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T10:20:37+00:00

This is a rather basic question, but it’s one that’s bugged me for awhile.

  • 0

This is a rather basic question, but it’s one that’s bugged me for awhile.

My project has a bunch of .cpp (Implementation) and .hpp (Definition) files.

I find that as I add additional classes and more class inter-dependencies, I have to #include other header files. After a week or two, I end up with #include directives in lots of places. Later, I’ll try removing some of the #includes and discover that everything still works because some OTHER included class is also #including what I just removed.

Is there a simple, easy rule for putting in #includes that will stop this ugly mess from happening in the first place? What is the best practice?

For example, I’ve worked on projects where the Implementation .cpp file ONLY includes the corresponding Definition .hpp file, and nothing else. If there are any other .hpp files that need to be used by the Implementation .cpp, they are all referenced by the Definition .hpp file.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I always use the principle of least coupling. I only include a file if the current file actually needs it; if I can get away with a forward declaration instead of a full definition, I’ll use that instead. My .cpp files always have a pile of #includes at the top.

    Bar.h:

    class Foo;  class Bar {     Foo * m_foo; };

    Bar.cpp:

    #include 'Foo.h' #include 'Bar.h'
    • 0