Skip to content

Commit b3f05c1

Browse files
authored
Trim superfluous space between parentheses and backticks
1 parent 9980870 commit b3f05c1

File tree

85 files changed

+135
-135
lines changed

Some content is hidden

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

85 files changed

+135
-135
lines changed

docs/assembler/inline/defining-asm-blocks-as-c-macros.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ C macros offer a convenient way to insert assembly code into your source code, b
1515

1616
- Put the **`__asm`** keyword in front of each assembly instruction.
1717

18-
- Use old-style C comments ( `/* comment */`) instead of assembly-style comments ( `; comment`) or single-line C comments ( `// comment`).
18+
- Use old-style C comments (`/* comment */`) instead of assembly-style comments (`; comment`) or single-line C comments (`// comment`).
1919

2020
To illustrate, the following example defines a simple macro:
2121

@@ -39,7 +39,7 @@ The third and fourth **`__asm`** keywords are needed as statement separators. Th
3939
4040
The braces are essential as well. If you omit them, the compiler can be confused by C or C++ statements on the same line to the right of the macro invocation. Without the closing brace, the compiler cannot tell where assembly code stops, and it sees C or C++ statements after the **`__asm`** block as assembly instructions.
4141
42-
Assembly-style comments that start with a semicolon (**;**) continue to the end of the line. This causes problems in macros because the compiler ignores everything after the comment, all the way to the end of the logical line. The same is true of single-line C or C++ comments ( `// comment`). To prevent errors, use old-style C comments ( `/* comment */`) in **`__asm`** blocks defined as macros.
42+
Assembly-style comments that start with a semicolon (**;**) continue to the end of the line. This causes problems in macros because the compiler ignores everything after the comment, all the way to the end of the logical line. The same is true of single-line C or C++ comments (`// comment`). To prevent errors, use old-style C comments (`/* comment */`) in **`__asm`** blocks defined as macros.
4343
4444
An **`__asm`** block written as a C macro can take arguments. Unlike an ordinary C macro, however, an **`__asm`** macro cannot return a value. So you cannot use such macros in C or C++ expressions.
4545

docs/atl-mfc-shared/reference/coledatetime-class.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -211,7 +211,7 @@ Following is a brief description of each constructor:
211211
212212
- `COleDateTime(` `dateSrc` **)** Constructs a `COleDateTime` object from an existing `COleDateTime` object.
213213
214-
- `COleDateTime(` *varSrc* **)** Constructs a `COleDateTime` object. Attempts to convert a `VARIANT` structure or [COleVariant](../../mfc/reference/colevariant-class.md) object to a date/time ( `VT_DATE`) value. If this conversion is successful, the converted value is copied into the new `COleDateTime` object. If it is not, the value of the `COleDateTime` object is set to 0 (midnight, 30 December 1899) and its status to invalid.
214+
- `COleDateTime(` *varSrc* **)** Constructs a `COleDateTime` object. Attempts to convert a `VARIANT` structure or [COleVariant](../../mfc/reference/colevariant-class.md) object to a date/time (`VT_DATE`) value. If this conversion is successful, the converted value is copied into the new `COleDateTime` object. If it is not, the value of the `COleDateTime` object is set to 0 (midnight, 30 December 1899) and its status to invalid.
215215
216216
- `COleDateTime(` `dtSrc` **)** Constructs a `COleDateTime` object from a `DATE` value.
217217
@@ -263,7 +263,7 @@ Indicates one of the following locale flags:
263263
Indicates locale ID to use for the conversion. For more information about language identifiers, see [Language Identifiers](/windows/win32/Intl/language-identifiers).
264264

265265
*lpszFormat*<br/>
266-
A formatting string similar to the `printf` formatting string. Each formatting code, preceded by a percent ( `%`) sign, is replaced by the corresponding `COleDateTime` component. Other characters in the formatting string are copied unchanged to the returned string. For more information, see the run-time function [strftime](../../c-runtime-library/reference/strftime-wcsftime-strftime-l-wcsftime-l.md). The value and meaning of the formatting codes for `Format` are:
266+
A formatting string similar to the `printf` formatting string. Each formatting code, preceded by a percent (`%`) sign, is replaced by the corresponding `COleDateTime` component. Other characters in the formatting string are copied unchanged to the returned string. For more information, see the run-time function [strftime](../../c-runtime-library/reference/strftime-wcsftime-strftime-l-wcsftime-l.md). The value and meaning of the formatting codes for `Format` are:
267267

268268
- `%H` Hours in the current day
269269

docs/atl-mfc-shared/reference/cstringt-class.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -486,11 +486,11 @@ A handle for a **`CStringT`** object.
486486

487487
Because the constructors copy the input data into new allocated storage, memory exceptions may result. Some of these constructors act as conversion functions. This allows you to substitute, for example, an **`LPTSTR`** where a **`CStringT`** object is expected.
488488

489-
- **`CStringT`**( `LPCSTR` `lpsz` ): Constructs a Unicode **`CStringT`** from an ANSI string. You can also use this constructor to load a string resource as shown in the example below.
489+
- **`CStringT`**(`LPCSTR` `lpsz`): Constructs a Unicode **`CStringT`** from an ANSI string. You can also use this constructor to load a string resource as shown in the example below.
490490

491-
- `CStringT(` `LPCWSTR` `lpsz` ): Constructs a **`CStringT`** from a Unicode string.
491+
- **`CStringT`**(`LPCWSTR` `lpsz`): Constructs a **`CStringT`** from a Unicode string.
492492

493-
- **`CStringT`**( `const unsigned char*` `psz` ): Allows you to construct a **`CStringT`** from a pointer to **`unsigned char`**.
493+
- **`CStringT`**(`const unsigned char*` `psz`): Allows you to construct a **`CStringT`** from a pointer to **`unsigned char`**.
494494

495495
> [!NOTE]
496496
> Define the `_CSTRING_DISABLE_NARROW_WIDE_CONVERSION` macro to turn off implicit string conversion between ANSI and Unicode strings. The macro excludes from compilation constructors that support conversion.

docs/build/reference/gd-gr-gv-gz-calling-convention.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ For more information about calling conventions, see [Calling Conventions](../../
4444

4545
On x86 processors, all function arguments are passed on the stack from right to left. On ARM and x64 architectures, some arguments are passed by register and the rest are passed on the stack from right to left. The calling routine pops the arguments from the stack.
4646

47-
For C, the **`__cdecl`** naming convention uses the function name preceded by an underscore ( `_` ); no case translation is performed. Unless declared as `extern "C"`, C++ functions use a different name-decorating scheme. For more information, see [Decorated Names](decorated-names.md).
47+
For C, the **`__cdecl`** naming convention uses the function name preceded by an underscore (`_`); no case translation is performed. Unless declared as `extern "C"`, C++ functions use a different name-decorating scheme. For more information, see [Decorated Names](decorated-names.md).
4848

4949
## __fastcall Specifics
5050

docs/c-runtime-library/reference/fopen-wfopen.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ Valid characters for the *`mode`* string that is used in **`fopen`** and **`_fdo
136136
| Characters in *`mode`* string | Equivalent *`oflag`* value for `_open`/`_sopen` |
137137
|--|--|
138138
| **`a`** | `_O_WRONLY | _O_APPEND` (usually `_O_WRONLY | _O_CREAT | _O_APPEND`) |
139-
| **`a+`** | `_O_RDWR | _O_APPEND` (usually `_O_RDWR | _O_APPEND | _O_CREAT` ) |
139+
| **`a+`** | `_O_RDWR | _O_APPEND` (usually `_O_RDWR | _O_APPEND | _O_CREAT`) |
140140
| **`r`** | `_O_RDONLY` |
141141
| **`r+`** | `_O_RDWR` |
142142
| **`w`** | `_O_WRONLY` (usually `_O_WRONLY | _O_CREAT | _O_TRUNC`) |

docs/c-runtime-library/reference/malloca.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ If *`size`* is greater than `_ALLOCA_S_THRESHOLD`, then **`_malloca`** attempts
3838

3939
There are restrictions to explicitly calling **`_malloca`** in an exception handler (EH). EH routines that run on x86-class processors operate in their own memory frame: They perform their tasks in memory space that isn't based on the current location of the stack pointer of the enclosing function. The most common implementations include Windows NT structured exception handling (SEH) and C++ catch clause expressions. Therefore, explicitly calling **`_malloca`** in any of the following scenarios results in program failure during the return to the calling EH routine:
4040

41-
- Windows SEH exception filter expression: **`__except`** (`_malloca ()` )
41+
- Windows SEH exception filter expression: **`__except`** (`_malloca ()`)
4242

4343
- Windows SEH final exception handler: **`__finally`** {`_malloca ()` }
4444

docs/c-runtime-library/reference/splitpath-wsplitpath.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Full path.
4141
Drive letter, followed by a colon (**:**). You can pass `NULL` for this parameter if you don't need the drive letter.
4242

4343
*`dir`*\
44-
Directory path, including trailing slash. Forward slashes ( `/` ), backslashes ( `\` ), or both may be used. Pass `NULL` for this parameter if you don't need the directory path.
44+
Directory path, including trailing slash. Forward slashes (`/`), backslashes (`\`), or both may be used. Pass `NULL` for this parameter if you don't need the directory path.
4545

4646
*`fname`*\
4747
Base filename (no extension). Pass `NULL` for this parameter if you don't need the filename.

docs/error-messages/compiler-errors-1/compiler-error-c2095.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@ ms.assetid: 44f8ada1-974f-4e81-a408-33ac6695aa53
1010

1111
'function' : actual parameter has type 'void' : parameter 'number'
1212

13-
The parameter passed to the function is type **`void`**, which is not allowed. Use a pointer to void ( `void *`) instead.
13+
The parameter passed to the function is type **`void`**, which is not allowed. Use a pointer to void (`void *`) instead.
1414

1515
The `number` indicates which parameter is **`void`**.

docs/error-messages/compiler-errors-1/compiler-error-c2100.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.assetid: 9ed5ea11-9d55-4ddf-8b1a-162c74f3c390
1010

1111
illegal indirection
1212

13-
Indirection operator ( `*` ) is applied to a nonpointer value.
13+
Indirection operator (`*`) is applied to a nonpointer value.
1414

1515
The following sample generates C2100:
1616

docs/error-messages/compiler-errors-1/compiler-error-c2110.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.assetid: 48fd76ed-90d6-4a60-9c7b-f6ce9355b4ca
1010

1111
'+' : cannot add two pointers
1212

13-
An attempt was made to add two pointer values using the plus ( `+` ) operator.
13+
An attempt was made to add two pointer values using the plus (`+`) operator.
1414

1515
The following sample generates C2110:
1616

0 commit comments

Comments
 (0)