Skip to content

Commit cf5189f

Browse files
author
Colin Robertson
committed
A bit of formatting added.
1 parent 30979ab commit cf5189f

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/how-to-report-a-problem-with-the-visual-cpp-toolset.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -276,10 +276,12 @@ To prepare to validate that the preprocessed file still reproduces the problem,
276276

277277
Confirm that the preprocessed file still reproduces the problem, as above.
278278

279-
#### Steps for C++ Modules repros
279+
### Preprocessed C++ Modules repros
280280

281281
If you're using the Modules feature of the C++ compiler, there are some different steps required to create and validate a preprocessed repro.
282282

283+
#### To preprocess a source code file that uses a module
284+
283285
1. Capture the command line arguments used to build your repro, as described in [To report the contents of the command line](#to-report-the-contents-of-the-command-line).
284286

285287
1. Open the **Developer Command Prompt** that matches the Visual Studio version and configuration architecture used to build your project.
@@ -294,7 +296,7 @@ If you're using the Modules feature of the C++ compiler, there are some differen
294296

295297
1. In the developer command prompt console window, enter the command **cl /P** *arguments* *modulename.ixx*, where *arguments* is the list of arguments captured above, and *modulename.ixx* is the name of the file that creates the module interface.
296298

297-
Finally, attach the preprocessed repros (filename.i and modulename.i) along with the .ifc output to your report.
299+
Finally, attach the preprocessed repros (*filename*.i and *modulename*.i) along with the .ifc output to your report.
298300

299301
### Link repros
300302

0 commit comments

Comments
 (0)