Is it possible to never use header guards in C/C++? If so, does this approach have any advantage?

user_11350573 0
Viewed 159

I have recently gotten into a project where the usage of header guards is forbidden as it is "bad design". Custom types are forward declared and headers are only included in cpp files.

This is the first project I have seen doing this and I find it quite uncomfortable to work with and if it were up to me I'd introduce the guards.

Using them has always been a given for me, so I don't even know how to argue against not using them other than highlighting the fact that it's uncomfortable. The project clearly compiles so in this case it's doable, but I'm left with a couple of questions:

  • Are there other scenarios where it would make the development impossible?
  • Does this style have a well-known benefit?
  • Are there known open source projects using this approach?
  • How would you convince the project leader to allow using guards?
header-files c++
2 Answers

I guess not including header in other header would cause maintaining list of headers in each translation unit (.cpp file).

If some dependency in one class on other is introduced, each header list is to be updated. Similarly, to take advantage of broken dependency, each list has to be updated too.

This does not look like a "good design".

user_29450270

Header guards are not "bad design". Refering to Bjarne Stroustrup and Herb Sutter:

SF.8: Use #include guards for all .h files

I would love to see the people behind your new project to argue with Stroustrup and Sutter over what is "bad design" in C++.

Forward declarations are a great tool, yes. But certainly not an answer to all situations. How would that work? You only have pointers as class members? You meticulously ensure nothing is defined in a header file?

ypnos_219740
Related