Why include guards?(为什么要加入守卫?)
问题描述
包含守卫,如此处所定义,用于防止两次加载相同的代码编译.
Include guards, as defined here, are used to prevent loading the same code twice at compilation.
为什么我的编译器 (GCC) 无法检测到它正在加载相同的代码两次并且具有合理的默认行为?
Why can't my compiler (GCC) detect that it is loading the same code twice and have a sensible default behaviour?
推荐答案
很简单,因为您可能希望编译器加载该文件两次.
Simply because you might have wanted the compiler to load that file twice.
请记住,#include
只是加载一个文件并将其内容放在指令的位置.该文件可能是头文件,但也可能是有用且经常使用的源代码.
Remember, that #include
simply loads a file and puts its contents in the place of the directive. This file might be a header file, but may be useful and frequently used piece of source code as well.
大多数现代编译器对 #pragma once
做出反应,完全按照您的意愿行事.但请记住,这是一个未包含在语言规范中的编译器扩展,坚持包含保护通常是个好主意 - 您会确定它适用于所有编译器和任何情况.
Most modern compilers react to #pragma once
doing exactly what you want them to. Remember though, that this is a compiler extension not included in the language specification and it is generally a good idea to stick to include guards - you'll be certain, that it works on every compiler and in any circumstances.
这篇关于为什么要加入守卫?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:为什么要加入守卫?


- 近似搜索的工作原理 2021-01-01
- C++ 协变模板 2021-01-01
- 一起使用 MPI 和 OpenCV 时出现分段错误 2022-01-01
- 与 int by int 相比,为什么执行 float by float 矩阵乘法更快? 2021-01-01
- 从python回调到c++的选项 2022-11-16
- 静态初始化顺序失败 2022-01-01
- Stroustrup 的 Simple_window.h 2022-01-01
- 如何对自定义类的向量使用std::find()? 2022-11-07
- STL 中有 dereference_iterator 吗? 2022-01-01
- 使用/clr 时出现 LNK2022 错误 2022-01-01