Merge pull request MicrosoftDocs#3293 from corob-msft/docs/corob/cpp-docs-2585-followup

Rewrite of command line parsing docs per cpp-docs 2585

Author: megvanhuygen

docs/c-language/customizing-c-command-line-processing.md

@@ -1,17 +1,20 @@
 ---
-title: "Customizing C Command-Line Processing"
-ms.date: "11/04/2016"
+title: "Customizing C command-line processing"
+description: "How to suppress `main` function argument and environment parameter handling in the runtime startup code."
+ms.date: 11/19/2020
 helpviewer_keywords: ["_spawn functions", "command line, processing", "command-line processing", "startup code, customizing command-line processing", "environment, environment-processing routine", "_setargv function", "command line, processing arguments", "suppressing environment processing", "_exec function"]
-ms.assetid: c20fa11d-b35b-4f3e-93b6-2cd5a1c3c993
 ---
-# Customizing C Command-Line Processing
+# Customizing C command-line processing
 
-If your program does not take command-line arguments, you can save a small amount of space by suppressing use of the library routine that performs command-line processing. This routine is called **_setargv** (or **_wsetargv** in the wide-character environment), as described in [Expanding Wildcard Arguments](../c-language/expanding-wildcard-arguments.md). To suppress its use, define a routine that does nothing in the file containing the **main** function and name it **_setargv** (or **_wsetargv** in the wide-character environment). The call to **_setargv** or **_wsetargv** is then satisfied by your definition of **_setargv** or **_wsetargv** , and the library version is not loaded.
+If your program doesn't take command-line arguments, you can suppress the command-line processing routine to save a small amount of space. To suppress its use, include the *`noarg.obj`* file (for both `main` and `wmain`) in your **`/link`** compiler options or your **`LINK`** command line.
 
-Similarly, if you never access the environment table through the `envp` argument, you can provide your own empty routine to be used in place of **_setenvp** (or **_wsetenvp**), the environment-processing routine.
+Similarly, if you never access the environment table through the *`envp`* argument, you can suppress the internal environment-processing routine. To suppress its use, include the *`noenv.obj`* file (for both `main` and `wmain`) in your **`/link`** compiler options or your **`LINK`** command line.
 
-If your program makes calls to the **_spawn** or **_exec** family of routines in the C run-time library, you should not suppress the environment-processing routine, since this routine is used to pass an environment from the spawning process to the new process.
+For more information on runtime startup linker options, see [Link options](../c-runtime-library/link-options.md).
+
+Your program might make calls to the `spawn` or `exec` family of routines in the C runtime library. If it does, you shouldn't suppress the environment-processing routine, since it's used to pass an environment from the parent process to the child process.
 
 ## See also
 
-[main Function and Program Execution](../c-language/main-function-and-program-execution.md)
+[`main` function and program execution](../c-language/main-function-and-program-execution.md)\
+[Link options](../c-runtime-library/link-options.md).

docs/c-language/expanding-wildcard-arguments.md

@@ -1,26 +1,24 @@
 ---
-title: "Expanding Wildcard Arguments"
-ms.date: "11/04/2016"
+title: "Expanding wildcard arguments"
+description: "How to use a linker option to process wildcard command-line arguments in your programs."
+ms.date: 11/20/2020
 helpviewer_keywords: ["asterisk wildcard", "question mark, wildcard", "expanding wildcard arguments", "wildcards, expanding"]
-ms.assetid: 80a11c4b-0199-420e-a342-cf1d803be5bc
 ---
-# Expanding Wildcard Arguments
+# Expanding wildcard arguments
 
-**Microsoft Specific**
+Wildcard argument expansion is Microsoft-specific.
 
-When you run a C program, you can use either of the two wildcards — the question mark (?) and the asterisk (*) — to specify filename and path arguments on the command line.
+When you run a C program, you can use either of the two wildcards, the question mark (**`?`**) and the asterisk (**`*`**), to specify filename and path arguments on the command line.
 
-By default, wildcards are not expanded in command-line arguments. You can replace the normal argument vector `argv` loading routine with a version that does expand wildcards by linking with the setargv.obj or wsetargv.obj file. If your program uses a `main` function, link with setargv.obj. If your program uses a `wmain` function, link with wsetargv.obj. Both of these have equivalent behavior.
+By default, wildcards aren't expanded in command-line arguments. You can replace the normal argument vector `argv` loading routine with a version that does expand wildcards by linking with the *`setargv.obj`* or *`wsetargv.obj`* file. If your program uses a `main` function, link with *`setargv.obj`*. If your program uses a `wmain` function, link with *`wsetargv.obj`*. Both of these have equivalent behavior. 
 
-To link with setargv.obj or wsetargv.obj, use the **/link** option. For example:
+To link with *`setargv.obj`* or *`wsetargv.obj`*, use the **`/link`** option. For example:
 
-**cl example.c /link setargv.obj**
+**`cl example.c /link setargv.obj`**
 
-The wildcards are expanded in the same manner as operating system commands. (See your operating system user's guide if you are unfamiliar with wildcards.)
-
-**END Microsoft Specific**
+The wildcards are expanded in the same manner as operating system commands.
 
 ## See also
 
-[Link Options](../c-runtime-library/link-options.md)<br/>
-[main Function and Program Execution](../c-language/main-function-and-program-execution.md)
+[Link options](../c-runtime-library/link-options.md)\
+[`main` function and program execution](../c-language/main-function-and-program-execution.md)