For the latest documentation on Visual Studio 2017 RC, see Visual Studio 2017 RC Documentation.
Specifies that the file will be included (opened) only once by the compiler when compiling a source code file.
The use of
#pragma once can reduce build times as the compiler will not open and read the file after the first #include of the file in the translation unit. This is referred to as multiple-include optimization. It has an effect similar to the #include guard idiom, which uses preprocessor macro definitions to prevent multiple inclusion of the contents of the file. This also helps to prevent violations of the one definition rule—the requirement that all templates, types, functions, and objects have no more than one definition in your code.
// header.h #pragma once // Code placed here is included only once per translation unit
We recommend the
#pragma once directive for new code because it doesn't pollute the global namespace with a preprocessor symbol. It requires less typing, is less distracting, and can't cause symbol collisions—errors caused when different header files use the same preprocessor symbol as the guard value. It is not part of the C++ Standard, but it is implemented portably by several common compilers.
There is no advantage to use of both the #include guard idiom and
#pragma once in the same file. The compiler recognizes the #include guard idiom and implements the multiple include optimization the same way as the
#pragma once directive if no non-comment code or preprocessor directive comes before or after the standard form of the idiom:
// header.h // Demonstration of the #include guard idiom. // Note that the defined symbol can be arbitrary. #ifndef HEADER_H_ // equivalently, #if !defined HEADER_H_ #define HEADER_H_ // Code placed here is included only once per translation unit #endif // HEADER_H_
We recommend the #include guard idiom when code must be portable to compilers that do not implement the
#pragma once directive, to maintain consistency with existing code, or when the multiple-include optimization is impossible. This can occur in complex projects when file system aliasing or aliased include paths prevent the compiler from identifying identical include files by canonical path.
Be careful not to use
#pragma once or the #include guard idiom in header files that are designed to be included multiple times, using preprocessor symbols to control their effects. For an example of this design, see the <assert.h> header file. Also be careful to manage include paths to avoid creating multiple paths to included files, which can defeat the multiple-include optimization for both #include guards and