Skip to content

Commit f719f7b

Browse files
Merge pull request #6039 from MicrosoftDocs/main
Auto Publish – main to live - 2025-08-11 17:30 UTC
2 parents 2b7e7be + 6ea7f26 commit f719f7b

File tree

63 files changed

+181
-203
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

63 files changed

+181
-203
lines changed

docs/build/reference/files-created-for-clr-projects.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,16 @@
11
---
2-
description: "Learn more about: Files Created for CLR Projects"
32
title: "Files Created for CLR Projects"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: Files Created for CLR Projects"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["Visual Studio C++ projects, CLR programming", ".NET applications, C++"]
6-
ms.assetid: 59ae9020-5f26-4ad0-bbdd-97c2e2023a20
76
---
87
# Files Created for CLR Projects
98

109
When you use Visual C++ templates to create your projects, several files are created, depending on which template you use. The following table lists all the files that are created by project templates for .NET Framework projects.
1110

1211
|File name|File description|
1312
|---------------|----------------------|
14-
|AssemblyInfo.cpp|The file that contains information (that is, attributes, files, resources, types, versioning information, signing information, and so on) for modifying the project's assembly metadata. For more information see [Assembly Concepts](/dotnet/framework/app-domains/assembly-contents).|
13+
|AssemblyInfo.cpp|The file that contains information (that is, attributes, files, resources, types, versioning information, signing information, and so on) for modifying the project's assembly metadata. For more information, see [Assembly Concepts](/dotnet/framework/app-domains/assembly-contents).|
1514
|*projname*.asmx|A text file that references managed classes that encapsulate the functionality of the XML Web service.|
1615
|*projname*.cpp|The main source file and entry point into the application that Visual Studio created for you. Identifies the project .dll file and the project namespace. Provide your own code in this file.|
1716
|*projname*.vsdisco|An XML deployment file containing links to other resources that describe the XML Web service.|

docs/build/reference/return-value-of-cl-exe.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Return Value of cl.exe"
32
title: "Return Value of cl.exe"
4-
ms.date: "09/05/2018"
3+
description: "Learn more about: Return Value of cl.exe"
4+
ms.date: 09/05/2018
55
helpviewer_keywords: ["cl.exe compiler, return value"]
6-
ms.assetid: 7c2d7f33-ee0d-4199-8ef4-75fe2b007670
76
---
87
# Return Value of cl.exe
98

@@ -13,7 +12,7 @@ The return value of cl.exe can be useful if you are compiling from a script, pow
1312

1413
There are too many possible error exit codes for cl.exe to list them all. You can look up an error code in the winerror.h or ntstatus.h files included in the Windows Software Development Kit in the %ProgramFiles(x86)%\Windows Kits\\<em>version</em>\Include\shared\ directory. Error codes returned in decimal must be converted to hexadecimal for search. For example, an error code of -1073741620 converted to hexadecimal is 0xC00000CC. This error is found in ntstatus.h, where the corresponding message is "The specified share name cannot be found on the remote server." For a downloadable list of Windows error codes, see [`[MS-ERREF]` Windows Error Codes](/openspecs/windows_protocols/MS-ERREF).
1514

16-
You can also use the error lookup utility in Visual Studio to find out what a compiler error message means. In a Visual Studio command shell, enter **errlook.exe** to start the utility; or in the Visual Studio IDE, on the menu bar, choose **Tools**, **Error Lookup**. Enter the error value to find the descriptive text associated with the error. For more information see [ERRLOOK Reference](errlook-reference.md).
15+
You can also use the error lookup utility in Visual Studio to find out what a compiler error message means. In a Visual Studio command shell, enter **errlook.exe** to start the utility; or in the Visual Studio IDE, on the menu bar, choose **Tools**, **Error Lookup**. Enter the error value to find the descriptive text associated with the error. For more information, see [ERRLOOK Reference](errlook-reference.md).
1716

1817
## Remarks
1918

docs/c-language/c-comments.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: C Comments"
32
title: "C Comments"
4-
ms.date: "06/25/2018"
3+
description: "Learn more about: C Comments"
4+
ms.date: 06/25/2018
55
helpviewer_keywords: ["code comments, C code", "comments, documenting code", "comments, C code", "/* */ comment delimiters", "comments"]
6-
ms.assetid: 0f5f2825-e673-49e7-8669-94e2f5294989
76
---
87
# C Comments
98

@@ -57,7 +56,7 @@ The Microsoft compiler also supports single-line comments preceded by two forwar
5756
// This is a valid comment
5857
```
5958

60-
Comments beginning with two forward slashes (**`//`**) are terminated by the next newline character that isn't preceded by an escape character. In the next example, the newline character is preceded by a backslash (**`\`**), creating an "escape sequence." This escape sequence causes the compiler to treat the next line as part of the previous line. (For more information, see [Escape Sequences](../c-language/escape-sequences.md).)
59+
Comments beginning with two forward slashes (**`//`**) are terminated by the next newline character that isn't preceded by an escape character. In the next example, the newline character is preceded by a backslash (**`\`**), creating an "escape sequence." This escape sequence causes the compiler to treat the next line as part of the previous line. For more information, see [Escape Sequences](../c-language/escape-sequences.md).
6160

6261
```C
6362
// my comment \

docs/c-language/initializing-scalar-types.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Initializing Scalar Types"
32
title: "Initializing Scalar Types"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: Initializing Scalar Types"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["initializing scalar types", "register variables", "initialization, scalar types", "initializing variables, scalar types", "scalar types", "static variables, initializing", "automatic storage class, initializing scalar types", "automatic storage class", "types [C], initializing"]
6-
ms.assetid: 73c516f5-c3ad-4d56-ab3b-f2a82b621104
76
---
87
# Initializing Scalar Types
98

@@ -38,7 +37,7 @@ You can initialize variables of any type, as long as you obey the following rule
3837

3938
- Variables declared with the **`auto`** or **`register`** storage-class specifier are initialized each time execution control passes to the block in which they're declared. If you omit an initializer from the declaration of an **`auto`** or **`register`** variable, the initial value of the variable is undefined. For automatic and register values, the initializer isn't restricted to being a constant; it can be any expression involving previously defined values, even function calls.
4039

41-
- The initial values for external variable declarations and for all **`static`** variables, whether external or internal, must be constant expressions. (For more information, see [Constant Expressions](../c-language/c-constant-expressions.md).) Since the address of any externally declared or static variable is constant, it can be used to initialize an internally declared **`static`** pointer variable. However, the address of an **`auto`** variable can't be used as a static initializer because it may be different for each execution of the block. You can use either constant or variable values to initialize **`auto`** and **`register`** variables.
40+
- The initial values for external variable declarations and for all **`static`** variables, whether external or internal, must be constant expressions. For more information, see [Constant Expressions](../c-language/c-constant-expressions.md). Since the address of any externally declared or static variable is constant, it can be used to initialize an internally declared **`static`** pointer variable. However, the address of an **`auto`** variable can't be used as a static initializer because it may be different for each execution of the block. You can use either constant or variable values to initialize **`auto`** and **`register`** variables.
4241

4342
- If the declaration of an identifier has block scope, and the identifier has external linkage, the declaration can't have an initialization.
4443

docs/c-language/l-value-and-r-value-expressions.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: L-Value and R-Value Expressions"
32
title: "L-Value and R-Value Expressions"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: L-Value and R-Value Expressions"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["L-values", "member-selection expressions", "R-value expressions", "subscript expressions"]
6-
ms.assetid: b790303e-ec6f-4d0d-bc55-df42da267172
76
---
87
# L-Value and R-Value Expressions
98

@@ -31,7 +30,7 @@ The term "r-value" is sometimes used to describe the value of an expression and
3130

3231
**Microsoft Specific**
3332

34-
Microsoft C includes an extension to the ANSI C standard that allows casts of l-values to be used as l-values, as long as the size of the object isn't lengthened through the cast. (For more information, see [Type-Cast Conversions](../c-language/type-cast-conversions.md).) The following example illustrates this feature:
33+
Microsoft C includes an extension to the ANSI C standard that allows casts of l-values to be used as l-values, as long as the size of the object isn't lengthened through the cast. For more information, see [Type-Cast Conversions](../c-language/type-cast-conversions.md). The following example illustrates this feature:
3534

3635
```
3736
char *p ;

docs/c-language/parameters.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Parameters"
32
title: "Parameters"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: Parameters"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["arguments [C++], function", "function parameters", "parameters [C++]", "function arguments, vs. parameters", "parameters [C++], function", "functions [C], parameters", "function parameters, syntax", "ellipsis (...), parameters", "... ellipsis"]
6-
ms.assetid: 8f2b8026-78b5-4e21-86a3-bf0f91f05689
76
---
87
# Parameters
98

@@ -50,7 +49,7 @@ void new( double x, double y, double z )
5049
}
5150
```
5251

53-
If at least one parameter occurs in the parameter list, the list can end with a comma followed by three periods (**`, ...`**). This construction, called the "ellipsis notation," indicates a variable number of arguments to the function. (For more information, see [Calls with a Variable Number of Arguments](../c-language/calls-with-a-variable-number-of-arguments.md).) However, a call to the function must have at least as many arguments as there are parameters before the last comma.
52+
If at least one parameter occurs in the parameter list, the list can end with a comma followed by three periods (**`, ...`**). This construction, called the "ellipsis notation," indicates a variable number of arguments to the function. For more information, see [Calls with a Variable Number of Arguments](../c-language/calls-with-a-variable-number-of-arguments.md). However, a call to the function must have at least as many arguments as there are parameters before the last comma.
5453

5554
If no arguments are to be passed to the function, the list of parameters is replaced by the keyword **`void`**. This use of **`void`** is distinct from its use as a type specifier.
5655

docs/c-language/scope-and-visibility.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Scope and Visibility"
32
title: "Scope and Visibility"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: Scope and Visibility"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["scope, levels", "visibility", "file scope [C++]"]
6-
ms.assetid: a019eb7c-66ed-46a7-bc9f-89a963930a56
76
---
87
# Scope and Visibility
98

@@ -15,7 +14,7 @@ All identifiers except labels have their scope determined by the level at which
1514
The declarator or type specifier for an identifier with file scope appears outside any block or list of parameters and is accessible from any place in the translation unit after its declaration. Identifier names with file scope are often called "global" or "external." The scope of a global identifier begins at the point of its definition or declaration and terminates at the end of the translation unit.
1615

1716
**Function scope**\
18-
A label is the only kind of identifier that has function scope. A label is declared implicitly by its use in a statement. Label names must be unique within a function. (For more information about labels and label names, see [The goto and Labeled Statements](../c-language/goto-and-labeled-statements-c.md).)
17+
A label is the only kind of identifier that has function scope. A label is declared implicitly by its use in a statement. Label names must be unique within a function. For more information about labels and label names, see [The goto and Labeled Statements](../c-language/goto-and-labeled-statements-c.md).
1918

2019
**Block scope**\
2120
The declarator or type specifier for an identifier with block scope appears inside a block or within the list of formal parameter declarations in a function definition. It is visible only from the point of its declaration or definition to the end of the block containing its declaration or definition. Its scope is limited to that block and to any blocks nested in that block and ends at the curly brace that closes the associated block. Such identifiers are sometimes called "local variables."

docs/c-language/typedef-declarations.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Typedef Declarations"
32
title: "Typedef Declarations"
4-
ms.date: "11/04/2016"
3+
description: "Learn more about: Typedef Declarations"
4+
ms.date: 11/04/2016
55
helpviewer_keywords: ["declarations, typedef", "typedef declarations", "types [C], declarations"]
6-
ms.assetid: e92a3b82-9269-4bc6-834a-6f431ccac83e
76
---
87
# Typedef Declarations
98

@@ -43,7 +42,7 @@ A typedef declaration is interpreted in the same way as a variable or function d
4342

4443
A typedef declaration doesn't create new types. It creates synonyms for existing types, or names for types that could be specified in other ways. When a typedef name is used as a type specifier, it can be combined with certain type specifiers, but not others. Acceptable modifiers include **`const`** and **`volatile`**.
4544

46-
Typedef names share the name space with ordinary identifiers. (For more information, see [Name Spaces](../c-language/name-spaces.md).) Therefore, a program can have a typedef name and a local-scope identifier by the same name. For example:
45+
Typedef names share the name space with ordinary identifiers. For more information, see [Name Spaces](../c-language/name-spaces.md). Therefore, a program can have a typedef name and a local-scope identifier by the same name. For example:
4746

4847
```C
4948
typedef char FlagType;

docs/c-runtime-library/code-pages.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
22
title: "Code Pages"
33
description: "A description of code page support in the Microsoft C runtime."
4+
ms.date: 11/04/2016
45
ms.topic: "concept-article"
5-
ms.date: "11/04/2016"
66
helpviewer_keywords: ["character sets [C++], code pages", "ANSI [C++], code pages", "system-default code page", "multibyte code pages [C++]", "localization [C++], code pages", "code pages [C++], types of", "locale code pages [C++]"]
7-
ms.assetid: 4a26fc42-185a-4add-98bf-a7b314ae6186
87
---
98
# Code pages
109

@@ -22,7 +21,7 @@ The Microsoft runtime library uses the following types of code pages:
2221

2322
also sets the locale to the system-default ANSI code page.
2423

25-
- Locale code page. The behavior of several run-time routines is dependent on the current locale setting, which includes the locale code page. (For more information, see [Locale](./locale.md).) By default, all locale-dependent routines in the Microsoft run-time library use the code page that corresponds to the "C" locale. At run time, you can change or query the locale code page in use with a call to [`setlocale`](./reference/setlocale-wsetlocale.md).
24+
- Locale code page. The behavior of several run-time routines is dependent on the current locale setting, which includes the locale code page. For more information, see [Locale](./locale.md). By default, all locale-dependent routines in the Microsoft run-time library use the code page that corresponds to the "C" locale. At run time, you can change or query the locale code page in use with a call to [`setlocale`](./reference/setlocale-wsetlocale.md).
2625

2726
- Multibyte code page. The behavior of most of the multibyte-character routines in the run-time library depends on the current multibyte code page setting. By default, these routines use the system-default ANSI code page. At run-time you can query and change the multibyte code page with [`_getmbcp`](./reference/getmbcp.md) and [`_setmbcp`](./reference/setmbcp.md), respectively.
2827

docs/c-runtime-library/is-isw-routines.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,6 @@ Character has property specified by the `desc` argument. For each valid value of
126126
| `_LOWER` | `iswlower(c)` |
127127
| `_ALPHA | _BLANK | _DIGIT | _PUNCT` | `iswprint(c)` |
128128
| `_PUNCT` | `iswpunct(c)` |
129-
| `_BLANK` | `iswblank(c)` |
130129
| `_SPACE` | `iswspace(c)` |
131130
| `_UPPER` | `iswupper(c)` |
132131
| `_HEX` | `iswxdigit(c)` |

0 commit comments

Comments
 (0)