> ## Documentation Index > Fetch the complete documentation index at: https://docs.syntblaze.com/llms.txt > Use this file to discover all available pages before exploring further. # C++ System Include The `#include <...>` directive is a preprocessor command that instructs the C++ compiler to insert the contents of a specified standard library or system-level header file into the current translation unit. It specifically dictates the search path strategy the preprocessor uses to locate the file. ```cpp theme={"dark"} #include ``` ## Resolution Mechanics When the preprocessor encounters an `#include` directive utilizing angle brackets (`< >`), it initiates a search for the specified file across an implementation-defined list of standard system directories. 1. **Search Path:** The compiler looks in predefined system include paths (e.g., `/usr/include`, `/usr/local/include` on Unix-like systems, or paths specified by the IDE/toolchain on Windows). 2. **Compiler Flags:** This search path can be modified or appended to during compilation using specific flags (such as `-I` or `-isystem` in GCC/Clang, or `/I` in MSVC). 3. **Text Substitution:** Occurring during Phase 4 of the C++ translation process, the preprocessor performs a literal, recursive text substitution. The entire `#include` line is replaced by the raw text of the resolved header file before the code is passed to the compiler's parser. ## Angle Brackets (`< >`) vs. Quotes (`" "`) The distinction between angle brackets and quotation marks lies strictly in the order of directory traversal: * **`< >` (System Include):** Bypasses the local directory. The preprocessor immediately searches the standard system directories. * **`" "` (Local Include):** The preprocessor first searches the directory containing the current source file. If the file is not found locally, the preprocessor falls back to the system directory search path used by `< >`. ## C++ Standard Header Naming Conventions System includes in C++ follow specific naming conventions that dictate namespace behavior and file extensions: * **C++ Standard Library Headers:** Do not use a file extension. ```cpp theme={"dark"} #include #include ``` * **C Standard Library Headers in C++:** C system headers adapted for C++ are prefixed with the letter `c` and drop the `.h` extension. This guarantees that the included declarations are placed inside the `std::` namespace. ```cpp theme={"dark"} #include // C++ equivalent of C's #include // C++ equivalent of C's ``` * **POSIX/OS-Specific Headers:** System-level APIs that are not part of the C++ standard typically retain their `.h` extensions. ```cpp theme={"dark"} #include #include ``` ## Idempotence and the ODR Because system headers are often included by multiple files within the same project, they are designed to be idempotent. They utilize include guards (`#ifndef`, `#define`, `#endif`) or the `#pragma once` directive. This ensures that even if a system include is resolved multiple times in a single translation unit, its contents are only processed once, preventing violations of the One Definition Rule (ODR).

Tired of Poor C++ Skills? Fix That With Deep Grasping! Learn More