blocks|key|392371|text|从编译时间的角度来看，这绝对是一种糟糕的做法，因为每次修改文件或接触任何包含的头文件时，都必须从头开始重新编译项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|392372|根据经验，您应该在源文件中包含尽可能少的头文件。然而，我可以看到一些情况下，这可能会派上用场，因为第三方库不会经常更改|392373|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

definitely a bad practice from the compilation time standpoint, since your project will have to be re-compiled from scratch everytime the file is modified or any of the included header is touched.

as a rule of thumb, you should include as few header as possible in your source files.
However I can see some situations where this could come handy, with 3rd party libs that don't change very often

blocks|key|5869145|text|由于编译C%2B%2B的成本很高，而且特别慢，我想说，如果有很多头文件(或者有很多实现文件，而这些文件又包含了头文件)，那么通过避免不必要地包含未使用的头文件，可以避免一些额外的预处理和解析时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5869146|这是针对库的实现的(您提到游戏引擎使我认为我们在这里谈论的是库)。现在，为了方便起见，您可以创建一个“主”包含文件，包括那些使用库并希望所有内容都放在一个地方的用户(而不是同时拥有数千个文件)。|5869147|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Since compiling C++ is expensive and can be particularly slow, I'd say you can avoid some extra pre-processing and parsing time by avoiding unnecessary inclusion of unused headers if there are a lot of header files (or there are a lot of implementation files which in turn include headers).

That's for the implementation of the library (you referring to game engines makes me think we're talking about libraries here). Now you can definitely make a "master" include file for convenience that those would include who use the library and want everything at one place (and don't have thousands of files at the same time).

blocks|key|1022481|text|在我看来，由于不键入正确的头文件名称而获得的5秒时间，当然不值得因为这种方法而导致编译时间的潜在巨大增加。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1022482|我得说这是个糟糕的练习。|1022483|然而，正如H2CO3所说，向框架的最终用户提供使用主头文件的可能性可能会非常有帮助。如果我没记错的话，GTK就是这么做的。|1022484|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my opinion, the 5 seconds you gain by not typing the name of the right header file are certainly not worth the potentially enormous increase of compile time induced by this method.

I'd say this is bad pratice.

However, as H2CO3 said, offering the possibility to use a master header file to the end-user of a framework can be quite helpful. GTK does that if I remember well.

blocks|key|5869234|text|大多数答案都提到了编译时间，而忽略了这样一个事实，即预编译头文件具有巨大的编译时间优势，并且使用主头文件技术效果要好得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5869235|最好是，如果直接包含在没有主头文件的情况下，您的头文件应该可以工作(这使得测试更容易)。现代编译器已经优化了“如果包含多个文件则跳过头文件”的逻辑。|5869236|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Most of the answers are mentioning compile time, and ignoring the fact that precompilation of headers has huge compile time benefits, and works much better with the master header technique.

Preferably, your headers should work if directly included without a master header file (this makes testing easier). Modern compilers have optimized the "skip header file if multiply included" logic.

blocks|key|392540|text|我还想补充说，当库提供一个主标题时，只包含需要的头文件是一个相当糟糕的主意。经常发生的情况是，这样的头并不包括它需要的一切，而是取决于主头将包括之前需要的所有头的事实。因此，如果你是这个库的用户，你通常没有太多的选择，应该遵循它的作者建议的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|392541|这也是为什么有主头可能被认为是糟糕的做法-它使我上面描述的这种情况更难检测。|392542|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would also add that including only needed headers when library provides a master one is rather bad idea. It often happens that such header does not include everything it needs, but rather depends on fact that master header will include all required headers before. So, if you are user of the library you usually do not have much choice and should follow the way suggested by it's author.

This is also why having master header may be considered as bad practice - it makes it harder to detect such case as I described above.

blocks|key|2516079|text|我认为C%2B%2B中的一些问题--还有这个问题--你可以通过记住C%2B%2B的“咒语”来回答自己。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2516080|2516081|不会为你不使用的东西付费。|blockquote|2516082|2516083|2516084|尽可能节省用户(即代码/库的使用者)的计算成本(运行时和编译时)。不要污染命名空间，不要在编译器中抛出超过需要的东西(也包括语法、突出显示等)。我认为这是C%2B%2B的礼貌方式:)|2516085|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|K|$]]

I think that some questions in C++ - and also this one - you can answer yourself by remembering the C++ "mantra" 

<blockquote>
 don't pay for what you don't use. 
</blockquote>

Save your users (i.e. the consumers of your code / library) computational cost (run-time and compile-time) wherever possible. don't pollute a namespace and throw more stuff at the compiler (also at the syntax highlighter etc) than needed. I think it's C++'s way of being polite :)

I have seen quite a few projects (often game engines) where all the header includes are placed in a single header file which sometimes contains macros etc as well e.g.

<pre><code>// Master.h

#include "header1.h"
#include "header2.h"
#include "header3.h"
.
.
#include "headerN.h"
</code></pre>

Then when using code, the standard would be to only include Master.h file.

Other projects work on the basis that the source files should include only the headers they need.

What I want to know is if there is a definitive answer as to best practice, preferably with measurable results, or is it personal preference?

Master Include Files - Good or Bad Practice

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我见过相当多的项目(通常是游戏引擎)，所有的头文件都放在一个单独的头文件中，有时也包含宏等。// Master.h#include "header1.h"#include "header2.h"#include "header3.h"..#include "headerN.h"那么在使用代码时，标准就是只包含Maste...

问Master Include Files -好或坏的做法
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Master Include Files -好或坏的做法EN