Skip to content

Commit b3fcc74

Browse files
TylerMSFTTylerMSFT
authored andcommitted
acrolinx
1 parent fc4f526 commit b3fcc74

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

docs/build/reference/experimental-module.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ Enables experimental compiler support for modules, as specified by the draft C++
1515
1616
## Remarks
1717

18-
You can enable experimental modules support by use of the **/experimental:module** compiler option along with the [/std:c++latest](std-specify-language-standard-version.md) option. You can use **/experimental:module-** to disable module support explicitly.
18+
You can enable experimental modules support by use of the **`/experimental:module`** compiler option along with the [/std:c++latest](std-specify-language-standard-version.md) option. You can use **`/experimental:module-`** to disable module support explicitly.
1919

20-
This option is available starting in Visual Studio 2015 Update 1. As of Visual Studio 2019 version 16.2, Draft C++20 Standard modules are not fully implemented in the Microsoft C++ compiler. You can use the modules feature to create single-partition modules and to import the Standard Library modules provided by Microsoft. A module and the code that consumes it must be compiled with the same compiler options.
20+
This option is available starting in Visual Studio 2015 Update 1. As of Visual Studio 2019 version 16.2, Draft C++20 Standard modules aren't fully implemented in the Microsoft C++ compiler. You can use the modules feature to create single-partition modules and to import the Standard Library modules provided by Microsoft. A module and the code that consumes it must be compiled with the same compiler options.
2121

2222
For more information on modules and how to use and create them, see [Overview of modules in C++](../../cpp/modules-cpp.md).
2323

24-
Here's an example of the compiler command-line options used to create an export module from source file *ModuleName.ixx*:
24+
Here's an example of the compiler command-line options used to create an export module from source file *`ModuleName.ixx`*:
2525

2626
```cmd
2727
cl /EHsc /MD /experimental:module /export /module:name ModuleName /module:wrapper C:\Output\path\ModuleName.h /module:output C:\Output\path\ModuleName.ifc -c ModuleName.ixx
@@ -43,4 +43,4 @@ cl /EHsc /MD /experimental:module /export /module:name ModuleName /module:wrappe
4343
[`/exportHeader` (Create header units)](module-exportheader.md)\
4444
[`/reference` (Use named module IFC)](module-reference.md)\
4545
[`/translateInclude` (Translate include directives into import directives)](translateinclude.md)\
46-
[/Zc (Conformance)](zc-conformance.md)
46+
[`/Zc` (Conformance)](zc-conformance.md)

docs/build/reference/sourcedependencies-directives.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: "/sourceDependencies:directives (Report source-level dependencies and use an allow-list)"
2+
title: "/sourceDependencies:directives (Report source-level dependencies and use an allowlist)"
33
description: "Reference guide to the /sourceDependencies:directives compiler option in Microsoft C++."
44
ms.date: 04/13/2020
55
f1_keywords: ["/sourceDependencies:directives"]
66
helpviewer_keywords: ["/sourceDependencies:directives compiler option", "/sourceDependencies:directives"]
77
---
8-
# `/sourceDependencies:directives` (Report source-level dependencies and use an allow-list)
8+
# `/sourceDependencies:directives` (Report source-level dependencies and use an allowlist)
99

1010
This command-line switch generates a JSON file that details the source-level dependencies consumed during compilation. It also looks for a `header-units.json` file that specifies which header files can be converted to header units.
1111

@@ -23,7 +23,7 @@ This command-line option is similar to [`/sourceDependencies`](sourcedependencie
2323
## Arguments
2424

2525
*`-`*\
26-
If the single dash is provided then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
26+
If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
2727

2828
*`filename`*\
2929
The compiler writes the source dependency output to the specified filename, which may include a relative or absolute path.\
@@ -43,7 +43,7 @@ All file paths appear as absolute paths in the output.
4343

4444
This switch is used in combination with [`/translateInclude`](translateinclude.md).
4545

46-
`header-units.json` is used with the build system's **Scan Sources for Module Dependencies** to determine which header files can be compiled into a header unit. When this switch is specified, header files encountered in the scanned source files, that are also listed in `header-units.json`, are considered eligible to be compiled into header units. Files not in the list are instead treated as a normal `#include`.
46+
`header-units.json` is used with the build system's **Scan Sources for Module Dependencies** to determine which header files can be compiled into a header unit. When this switch is specified, header files found in the scanned source files, that are also listed in `header-units.json`, are considered eligible to be compiled into header units. Files not in the list are instead treated as a normal `#include`.
4747

4848
The compiler looks for `header-units.json` where the header being loaded is located. For more information about the format of this file, see [C++ header-units.json reference](..\header-unit-json-reference.md)
4949

docs/build/reference/sourcedependencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This command-line switch generates a JSON file that details the source-level dep
2121
## Arguments
2222

2323
*`-`*\
24-
If the single dash is provided then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
24+
If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
2525

2626
*`filename`*\
2727
The compiler writes the source dependency output to the specified filename, which may include a relative or absolute path.\

0 commit comments

Comments
 (0)