| General topics | ||||||||||||||||
| Flow control | ||||||||||||||||
| Conditional execution statements | ||||||||||||||||
| Iteration statements (loops) | ||||||||||||||||
| Jump statements | ||||||||||||||||
| Functions | ||||||||||||||||
| Function declaration | ||||||||||||||||
| Lambda function expression | ||||||||||||||||
inline specifier | ||||||||||||||||
| Dynamic exception specifications(until C++17*) | ||||||||||||||||
noexcept specifier(C++11) | ||||||||||||||||
| Exceptions | ||||||||||||||||
| Namespaces | ||||||||||||||||
| Types | ||||||||||||||||
| Specifiers | ||||||||||||||||
| ||||||||||||||||
| Storage duration specifiers | ||||||||||||||||
| Initialization | ||||||||||||||||
| Expressions | ||||||||||||||||
| Alternative representations | ||||||||||||||||
| Literals | ||||||||||||||||
| Boolean -Integer -Floating-point | ||||||||||||||||
| Character -String -nullptr(C++11) | ||||||||||||||||
| User-defined(C++11) | ||||||||||||||||
| Utilities | ||||||||||||||||
| Attributes(C++11) | ||||||||||||||||
| Types | ||||||||||||||||
typedef declaration | ||||||||||||||||
| Type alias declaration(C++11) | ||||||||||||||||
| Casts | ||||||||||||||||
| Memory allocation | ||||||||||||||||
| Classes | ||||||||||||||||
| Class-specific function properties | ||||||||||||||||
| ||||||||||||||||
| Special member functions | ||||||||||||||||
| Templates | ||||||||||||||||
| Miscellaneous | ||||||||||||||||
(C++23)(C++23) | ||||
(C++17) | ||||
(C++23) | ||||
#pragma_Pragma (C++11) | ||||
(C++26) |
Implementation defined behavior is controlled by#pragma directive.
Contents |
#pragmapragma-params | (1) | ||||||||
_Pragma(string-literal) | (2) | (since C++11) | |||||||
L prefix (if any), the outer quotes, and leading/trailing whitespace fromstring-literal, replaces each\" with" and each\\ with\, then tokenizes the result (as intranslation phase 3), and then uses the result as if the input to#pragma in(1).Pragma directive controls implementation-specific behavior of the compiler, such as disabling compiler warnings or changing alignment requirements. Any pragma that is not recognized is ignored.
The ISO C++ language standard does not require the compilers to support any pragmas. However, several non-standard pragmas are supported by multiple implementations:
ISO C language standard requires that C compilers support the following three pragmas, and some C++ compiler vendors support them, to varying degrees, in their C++ frontends:
#pragma STDC FENV_ACCESSarg | (1) | ||||||||
#pragma STDC FP_CONTRACTarg | (2) | ||||||||
#pragma STDC CX_LIMITED_RANGEarg | (3) | ||||||||
wherearg is eitherON,OFF, orDEFAULT.
ON, informs the compiler that the program will access or modifyfloating-point environment, which means that optimizations that could subvert flag tests and mode changes (e.g., global common subexpression elimination, code motion, and constant folding) are prohibited. The default value is implementation-defined, usuallyOFF.ON.OFF.The behavior of the program is undefined if any of the three pragmas above appear in any context other than outside all external declarations or preceding all explicit declarations and statements inside a compound statement.
Note: compilers that do not support these pragmas may provide equivalent compile-time options, such as gcc's-fcx-limited-range and-ffp-contract.
#pragma once is a non-standard pragma that is supported by thevast majority of modern compilers. If it appears in a header file, it indicates that it is only to be parsed once, even if it is (directly or indirectly) included multiple times in the same source file.
Standard approach to preventing multiple inclusion of the same header is by usinginclude guards:
#ifndef LIBRARY_FILENAME_H#define LIBRARY_FILENAME_H// contents of the header#endif /* LIBRARY_FILENAME_H */
So that all but the first inclusion of the header in any translation unit are excluded from compilation. All modern compilers record the fact that a header file uses an include guard and do not re-parse the file if it is encountered again, as long as the guard is still defined (see e.g.gcc).
With#pragma once, the same header appears as
#pragma once// contents of the header
Unlike header guards, this pragma makes it impossible to erroneously use the same macro name in more than one file. On the other hand, since with#pragma once files are excluded based on their filesystem-level identity, this can't protect against including a header twice if it exists in more than one location in a project.
This family of pragmas control the maximum alignment for subsequently defined class and union members.
#pragma pack(arg) | (1) | ||||||||
#pragma pack() | (2) | ||||||||
#pragma pack(push) | (3) | ||||||||
#pragma pack(push,arg) | (4) | ||||||||
#pragma pack(pop) | (5) | ||||||||
wherearg is a small power of two and specifies the new alignment in bytes.
#pragma pack may decrease the alignment of a class, however, it cannot make a class overaligned.
See also specific details forGCC andMSVC.
| This section is incomplete Reason: Explain the effects of this pragmas on data members and also the pros and cons of using them. Sources for reference: |
| This section is incomplete Reason: no example |
C documentation forImplementation defined behavior control |
| 1. | C++ pragmas in Visual Studio |
| 2. | Pragmas accepted by GCC |
| 3. | Individual pragma descriptions andStandard pragmas in IBM AIX XL C 16.1 |
| 4. | Appendix B. Pragmas in Sun Studio 11 C++ User's Guide |
| 5. | Intel C++ compiler pragmas |
| 6. | Release nodes (includes pragmas) for HP aCC A.06.25 |
