Merge pull request MicrosoftDocs#3373 from MicrosoftDocs/master

1/22/2021 AM Publish

Author: Taojunshen

docs/build/reference/i-additional-include-directories.md

@@ -6,51 +6,53 @@ f1_keywords: ["VC.Project.VCCLWCECompilerTool.AdditionalIncludeDirectories", "VC
 helpviewer_keywords: ["/I compiler option [C++]", "Additional Include Directories compiler option", "I compiler option [C++]", "-I compiler option [C++]", "set include directories", "include directories, compiler option [C++]"]
 ms.assetid: 3e9add2a-5ed8-4d15-ad79-5b411e313a49
 ---
-# /I (Additional include directories)
+# `/I` (Additional include directories)
 
 Adds a directory to the list of directories searched for include files.
 
 ## Syntax
 
-> **/I**[ ]*directory*
+> **`/I`** *directory*
 
 ### Arguments
 
-*directory*<br/>
-The directory to be added to the list of directories searched for include files.
+*directory*\
+The directory to add to the list of directories searched for include files. The space between `/I` and *directory* is optional. Directories that include spaces must be enclosed in double quotes. A directory may be an absolute path or a relative path.
 
 ## Remarks
 
 To add more than one directory, use this option more than once. Directories are searched only until the specified include file is found.
 
-You can use this option with the ([/X (Ignore Standard Include Paths)](x-ignore-standard-include-paths.md)) option.
+You can use this option on the same command line as the ([`/X` (Ignore standard include paths)](x-ignore-standard-include-paths.md)) option.
+
+A [`#include` directive](../../preprocessor/hash-include-directive-c-cpp.md) can be specified in double-quote (or local-first) form, for example, `#include "local.h"`. Or, it can be specified in angle-bracket (or include-path-first) form, for example, `#include <iostream>`.
 
 The compiler searches directories in the following order:
 
-1. If specified using a [#include directive](../../preprocessor/hash-include-directive-c-cpp.md) in double-quote form, it first searches local directories. The search begins in the same directory as the file that contains the **#include** statement. If this fails to find the file, it searches in the directories of the currently opened include files, in the reverse order in which they were opened. The search begins in the directory of the parent include file and continues upward through the directories of any grandparent include files.
+1. If the **`#include`** directive is specified using double-quote form, it first searches local directories. The search begins in the same directory as the file that contains the **`#include`** directive. If it fails to find the file, it searches next in the directories of the currently opened include files, in the reverse order in which they were opened. The search begins in the directory of the parent include file and continues upward through the directories of any grandparent include files.
 
-1. If specified using a **#include** directive in angle bracket form, or if the local directory search has failed, it searches directories specified by using the **/I** option, in the order that CL encounters them on the command line.
+1. If the **`#include`** directive is specified in angle-bracket form, or if the local directory search has failed, it searches directories specified by using the **`/I`** option, in the order they're specified on the command line.
 
-1. Directories specified in the **INCLUDE** environment variable.
+1. Directories specified in the **`INCLUDE`** environment variable.
 
 ### To set this compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
 1. Select the **Configuration Properties** > **C/C++** > **General** property page.
 
-1. Modify the **Additional Include Directories** property.
+1. Modify the **Additional Include Directories** property. You can specify more than one directory at a time in this property. Directories must be separated by a semicolon (**`;`**).
 
 ### To set this compiler option programmatically
 
 - See <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AdditionalIncludeDirectories%2A>.
 
 ## Example
 
-The following command looks for the include files requested by MAIN.c in the following order: First, if specified by using double-quotes, local files are searched. Next, search continues in the \INCLUDE directory, then in the \MY\INCLUDE directory, and finally in the directories assigned to the INCLUDE environment variable.
+The following command looks for the include files requested by *`main.c`* in the following order: First, if specified by using double-quotes, local files are searched. Next, search continues in the *`\include`* directory, then in the *`\my\include`* directory, and finally in the directories assigned to the **`INCLUDE`** environment variable, in left to right order.
 
-```
-CL /I \INCLUDE /I\MY\INCLUDE MAIN.C
+```cmd
+CL /I \include /I\my\include main.c
 ```
 
 ## See also

docs/build/reference/x-ignore-standard-include-paths.md

@@ -1,14 +1,14 @@
 ---
 description: "Learn more about: `/X` (Ignore standard include paths)"
 title: "/X (Ignore standard include paths)"
-ms.date: 07/31/2020
+ms.date: 01/21/2021
 f1_keywords: ["/x", "VC.Project.VCCLCompilerTool.OVERWRITEStandardIncludePath", "VC.Project.VCCLWCECompilerTool.OVERWRITEStandardIncludePath", "VC.Project.VCCLCompilerTool.IgnoreStandardIncludePath"]
 helpviewer_keywords: ["/X compiler option [C++]", "include files, ignore standard path", "-X compiler option [C++]", "include directories, ignore standard", "X compiler option", "Ignore Standard Include Paths compiler option"]
 ms.assetid: 16bdf2cc-c8dc-46e4-bdcc-f3caeba5e1ef
 ---
 # `/X` (Ignore standard include paths)
 
-Prevents the compiler from searching for include files in directories specified in the PATH and INCLUDE environment variables.
+Prevents the compiler from searching for include files in directories specified in the `PATH` and `INCLUDE` environment variables.
 
 ## Syntax
 
@@ -32,7 +32,7 @@ You can use this option with the [`/I` (Additional include directories)](i-addit
 
 ## Example
 
-In the following command, **`/X`** tells the compiler to ignore locations specified by the PATH and INCLUDE environment variables, and **`/I`** specifies the directory to look in for include files:
+In the following command, **`/X`** tells the compiler to ignore locations specified by the `PATH` and `INCLUDE` environment variables, and **`/I`** specifies the directory to look in for include files:
 
 ```cmd
 CL /X /I \ALT\INCLUDE MAIN.C

docs/code-quality/code-analysis-for-c-cpp-overview.md

@@ -40,7 +40,7 @@ C:\>cl /analyze Sample.cpp
 
 ## #pragma support
 
-You can use the `#pragma` directive to treat warnings as errors; enable or disable warnings, and suppress warnings for individual lines of code. For more information, see [Pragma Directives and the __Pragma Keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md).
+You can use the `#pragma` directive to treat warnings as errors; enable or disable warnings, and suppress warnings for individual lines of code. For more information, see [Pragma directives and the `__pragma` and `_Pragma` keywords](../preprocessor/pragma-directives-and-the-pragma-keyword.md).
 
 ## Annotation support
 

docs/preprocessor/alloc-text.md

@@ -1,35 +1,35 @@
 ---
-description: "Learn more about: alloc_text pragma"
+description: "Learn more about the alloc_text pragma directive in Microsoft C/C++"
 title: "alloc_text pragma"
-ms.date: "08/29/2019"
+ms.date: 01/22/2021
 f1_keywords: ["vc-pragma.alloc_text", "alloc_text_CPP"]
-helpviewer_keywords: ["alloc_text pragma", "pragmas, alloc_text"]
-ms.assetid: 1fd7be18-e4f7-4f70-b079-6326f72b871a
+helpviewer_keywords: ["alloc_text pragma", "pragma, alloc_text"]
+no-loc: ["pragma"]
 ---
-# alloc_text pragma
+# `alloc_text` pragma
 
-Names the code section where the specified function definitions are to reside. The pragma must occur between a function declarator and the function definition for the named functions.
+Names the code section where the specified function definitions are placed. The pragma must occur between a function declarator and the function definition for the named functions.
 
 ## Syntax
 
-> **#pragma alloc_text(** "*textsection*" **,** *function1* [**,** *function2* ... ] **)**
+> **`#pragma alloc_text(`** "*text-section*" **`,`** *function_1* [**`,`** *function_2* ... ] **`)`**
 
 ## Remarks
 
-The **alloc_text** pragma does not handle C++ member functions or overloaded functions. It is applicable only to functions declared with C linkage — that is, functions declared with the **extern "C"** linkage specification. If you attempt to use this pragma on a function with C++ linkage, a compiler error is generated.
+The **`alloc_text`** pragma doesn't handle C++ member functions or overloaded functions. It's applicable only to functions declared with C linkage, that is, functions declared with the **`extern "C"`** linkage specification. If you attempt to use this pragma on a function with C++ linkage, a compiler error is generated.
 
-Since function addressing using **`__based`** is not supported, specifying section locations requires the use of the **alloc_text** pragma. The name specified by *textsection* should be enclosed in double quotation marks.
+Since function addressing using **`__based`** isn't supported, specifying section locations requires the use of the **`alloc_text`** pragma. The name specified by *text-section* should be enclosed in double quotation marks.
 
-The **alloc_text** pragma must appear after the declarations of any of the specified functions and before the definitions of these functions.
+The **`alloc_text`** pragma must appear after the declarations of any of the specified functions and before the definitions of these functions.
 
-Functions referenced in an **alloc_text** pragma should be defined in the same module as the pragma. Otherwise, if an undefined function is later compiled into a different text section, the error may or may not be caught. Although the program will usually run correctly, the function will not be allocated in the intended sections.
+Functions referenced in an **`alloc_text`** pragma should be defined in the same module as the pragma. Otherwise, if an undefined function is later compiled into a different text section, the error may or may not be caught. Although the program will usually run correctly, the function won't be allocated in the intended sections.
 
-Other limitations on **alloc_text** are as follows:
+Other limitations on **`alloc_text`** are as follows:
 
 - It can't be used inside a function.
 
 - It must be used after the function has been declared, but before the function has been defined.
 
 ## See also
 
-[Pragma directives and the __pragma keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+[Pragma directives and the `__pragma` and `_Pragma` keywords](./pragma-directives-and-the-pragma-keyword.md)

docs/preprocessor/auto-inline.md

@@ -1,23 +1,23 @@
 ---
-description: "Learn more about: auto_inline pragma"
+description: "Learn more about the auto_inline pragma directive in Microsoft C/C++"
 title: "auto_inline pragma"
-ms.date: "08/29/2019"
+ms.date: 01/22/2021
 f1_keywords: ["auto_inline_CPP", "vc-pragma.auto_inline"]
-helpviewer_keywords: ["pragmas, auto_inline", "auto_inline pragma"]
-ms.assetid: f7624cd1-be76-429a-881c-65c9040acf43
+helpviewer_keywords: ["pragma, auto_inline", "auto_inline pragma"]
+no-loc: ["pragma"]
 ---
-# auto_inline pragma
+# `auto_inline` pragma
 
-Excludes any functions defined within the range where **off** is specified from being considered as candidates for automatic inline expansion.
+Excludes any functions defined within the range where **`off`** is specified from being considered as candidates for automatic inline expansion.
 
 ## Syntax
 
-> **#pragma auto_inline(** [ { **on** | **off** } ] **)**
+> **`#pragma auto_inline(`** [ { **`on`** | **`off`** } ] **`)`**
 
 ## Remarks
 
-To use the **auto_inline** pragma, place it before and immediately after, not inside, a function definition. The pragma takes effect as soon as the first function definition after the pragma is seen.
+To use the **`auto_inline`** pragma, place it before and immediately after, not inside, a function definition. The pragma takes effect as soon as the first function definition after the pragma is seen.
 
 ## See also
 
-[Pragma directives and the __pragma keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+[Pragma directives and the `__pragma` and `_Pragma` keywords](./pragma-directives-and-the-pragma-keyword.md)

docs/preprocessor/bss-seg.md

@@ -1,33 +1,33 @@
 ---
-description: "Learn more about: bss_seg pragma"
+description: "Learn more about the bss_seg pragma directive in Microsoft C/C++"
 title: "bss_seg pragma"
-ms.date: "08/29/2019"
+ms.date: 01/22/2021
 f1_keywords: ["vc-pragma.bss_seg", "bss_seg_CPP"]
-helpviewer_keywords: ["pragmas, bss_seg", "bss_seg pragma"]
-ms.assetid: 755f0154-de51-4778-97d3-c9b24e445079
+helpviewer_keywords: ["pragma, bss_seg", "bss_seg pragma"]
+no-loc: ["pragma"]
 ---
-# bss_seg pragma
+# `bss_seg` pragma
 
 Specifies the section (segment) where uninitialized variables are stored in the object (.obj) file.
 
 ## Syntax
 
-> **#pragma bss_seg(** [ "*section-name*" [ **,** "*section-class*" ] ] **)**\
-> **#pragma bss_seg(** { **push** | **pop** } [ **,** *identifier* ] [ **,** "*section-name*" [ **,** "*section-class*" ] ] **)**
+> **`#pragma bss_seg(`** [ "*section-name*" [ **`,`** "*section-class*" ] ] **`)`**\
+> **`#pragma bss_seg(`** { **`push`** | **`pop`** } [ **`,`** *identifier* ] [ **`,`** "*section-name*" [ **`,`** "*section-class*" ] ] **`)`**
 
 ### Parameters
 
-**push**\
-(Optional) Puts a record on the internal compiler stack. A **push** can have an *identifier* and *section-name*.
+**`push`**\
+(Optional) Puts a record on the internal compiler stack. A **`push`** can have an *identifier* and *section-name*.
 
-**pop**\
-(Optional) Removes a record from the top of the internal compiler stack. A **pop** can have an *identifier* and *section-name*. You can pop multiple records using just one **pop** command by using the *identifier*. The *section-name* becomes the active BSS section name after the pop.
+**`pop`**\
+(Optional) Removes a record from the top of the internal compiler stack. A **`pop`** can have an *identifier* and *section-name*. You can pop multiple records using just one **`pop`** command by using the *identifier*. The *section-name* becomes the active BSS section name after the pop.
 
 *identifier*\
-(Optional) When used with **push**, assigns a name to the record on the internal compiler stack. When used with **pop**, the directive pops records off the internal stack until *identifier* is removed. If *identifier* isn't found on the internal stack, nothing is popped.
+(Optional) When used with **`push`**, assigns a name to the record on the internal compiler stack. When used with **`pop`**, the directive pops records off the internal stack until *identifier* is removed. If *identifier* isn't found on the internal stack, nothing is popped.
 
 *"section-name"*\
-(Optional) The name of a section. When used with **pop**, the stack is popped and *section-name* becomes the active BSS section name.
+(Optional) The name of a section. When used with **`pop`**, the stack is popped and *section-name* becomes the active BSS section name.
 
 *"section-class"*\
 (Optional) Ignored, but included for compatibility with versions of Microsoft C++ earlier than version 2.0.
@@ -36,13 +36,13 @@ Specifies the section (segment) where uninitialized variables are stored in the
 
 A *section* in an object file is a named block of data that's loaded into memory as a unit. A *BSS section* is a section that contains uninitialized data. In this article, the terms *segment* and *section* have the same meaning.
 
-The **bss_seg** pragma directive tells the compiler to put all uninitialized data items from the translation unit into a BSS section named *section-name*. In some cases, use of **bss_seg** can speed load times by grouping uninitialized data into one section. By default, the BSS section used for uninitialized data in an object file is named `.bss`. A **bss_seg** pragma directive without a *section-name* parameter resets the BSS section name for the subsequent uninitialized data items to `.bss`.
+The **`bss_seg`** pragma directive tells the compiler to put all uninitialized data items from the translation unit into a BSS section named *section-name*. In some cases, use of **`bss_seg`** can speed load times by grouping uninitialized data into one section. By default, the BSS section used for uninitialized data in an object file is named `.bss`. A **`bss_seg`** pragma directive without a *section-name* parameter resets the BSS section name for the subsequent uninitialized data items to `.bss`.
 
-Data allocated using the **bss_seg** pragma does not retain any information about its location.
+Data allocated using the **`bss_seg`** pragma does not retain any information about its location.
 
-For a list of names that shouldn't be used to create a section, see [/SECTION](../build/reference/section-specify-section-attributes.md).
+For a list of names that shouldn't be used to create a section, see [`/SECTION`](../build/reference/section-specify-section-attributes.md).
 
-You can also specify sections for initialized data ([data_seg](../preprocessor/data-seg.md)), functions ([code_seg](../preprocessor/code-seg.md)), and const variables ([const_seg](../preprocessor/const-seg.md)).
+You can also specify sections for initialized data ([`data_seg`](../preprocessor/data-seg.md)), functions ([`code_seg`](../preprocessor/code-seg.md)), and const variables ([`const_seg`](../preprocessor/const-seg.md)).
 
 You can use the [DUMPBIN.EXE](../build/reference/dumpbin-command-line.md) application to view object files. Versions of DUMPBIN for each supported target architecture are included with Visual Studio.
 
@@ -66,4 +66,4 @@ int main() {
 
 ## See also
 
-[Pragma directives and the __pragma keyword](../preprocessor/pragma-directives-and-the-pragma-keyword.md)
+[Pragma directives and the `__pragma` and `_Pragma` keywords](./pragma-directives-and-the-pragma-keyword.md)