C++头文件的包含顺序研究

最新推荐文章于 2022-09-13 22:40:09 发布

这个看起来廋

最新推荐文章于 2022-09-13 22:40:09 发布

阅读量389

点赞数

本文链接：https://blog.csdn.net/qq_43679402/article/details/86689425

版权

作者：朱金灿

来源：http://blog.csdn.net/clever101

一．《Google C++ 编程风格指南》里的观点

公司在推行编码规范，领导提议基本上使用《Google C++ 编程风格指南》。其中《Google C++ 编程风格指南》对于头文件的包含顺序是这样的：

Names and Order of Includes

link ▽Use standard order for readability and to avoid hidden dependencies:C library, C++ library, other libraries' .h, your project's .h.

All of a project's header files should belisted as descendants of the project's source directory without use of UNIXdirectory shortcuts . (the current directory) or .. (the parent directory). Forexample, google-awesome-project/src/base/logging.h should be included as

#include "base/logging.h"

In dir/foo.cc or dir/foo_test.cc, whosemain purpose is to implement or test the stuff in dir2/foo2.h, order yourincludes as follows:

dir2/foo2.h (preferred location — seedetails below).

C system files.

C++ system files.

Other libraries' .h files.

Your project's .h files.

The preferred ordering reduces hiddendependencies. We want every header file to be compilable on its own. Theeasiest way to achieve this is to make sure that every one of them is the first.h file #included in some .cc.

dir/foo.cc and dir2/foo2.h are often in thesame directory (e.g. base/basictypes_test.cc and base/basictypes.h), but can bein different directories too.

Within each section it is nice to order theincludes alphabetically.

For example, the includes ingoogle-awesome-project/src/foo/internal/fooserver.cc might look like this:

#include "foo/public/fooserver.h"  // Preferred location.#include <sys/types.h>#include <unistd.h> #include <hash_map>#include <vector> #include "base/basictypes.h"#include"base/commandlineflags.h"#include "foo/public/bar.h"