You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/c-runtime-library/buffer-manipulation.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -13,14 +13,14 @@ Use these routines to work with areas of memory on a byte-by-byte basis.
13
13
14
14
|Routine|Use|
15
15
|-------------|---------|
16
-
|[_memccpy](./reference/memccpy.md)|Copy characters from one buffer to another until given character or given number of characters has been copied|
17
-
|[memchr, wmemchr](./reference/memchr-wmemchr.md)|Return pointer to first occurrence, within specified number of characters, of given character in buffer|
18
-
|[memcmp, wmemcmp](./reference/memcmp-wmemcmp.md)|Compare specified number of characters from two buffers|
19
-
|[memcpy, wmemcpy](./reference/memcpy-wmemcpy.md), [memcpy_s, wmemcpy_s](./reference/memcpy-s-wmemcpy-s.md)|Copy specified number of characters from one buffer to another|
20
-
|[_memicmp, _memicmp_l](./reference/memicmp-memicmp-l.md)|Compare specified number of characters from two buffers without regard to case|
21
-
|[memmove, wmemmove](./reference/memmove-wmemmove.md),[memmove_s, wmemmove_s](./reference/memmove-s-wmemmove-s.md)|Copy specified number of characters from one buffer to another|
22
-
|[memset, wmemset](./reference/memset-wmemset.md)|Use given character to initialize specified number of bytes in the buffer|
23
-
|[_swab](./reference/swab.md)|Swap bytes of data and store them at specified location|
16
+
|[`_memccpy`](./reference/memccpy.md)|Copy characters from one buffer to another until given character or given number of characters has been copied|
17
+
|[`memchr`, `wmemchr`](./reference/memchr-wmemchr.md)|Return pointer to first occurrence, within specified number of characters, of given character in buffer|
18
+
|[`memcmp`, `wmemcmp`](./reference/memcmp-wmemcmp.md)|Compare specified number of characters from two buffers|
19
+
|[`memcpy`, `wmemcpy`](./reference/memcpy-wmemcpy.md), [`memcpy_s`, `wmemcpy_s`](./reference/memcpy-s-wmemcpy-s.md)|Copy specified number of characters from one buffer to another|
20
+
|[`_memicmp`, `_memicmp_l`](./reference/memicmp-memicmp-l.md)|Compare specified number of characters from two buffers without regard to case|
21
+
|[`memmove`, `wmemmove`](./reference/memmove-wmemmove.md),[`memmove_s`, `wmemmove_s`](./reference/memmove-s-wmemmove-s.md)|Copy specified number of characters from one buffer to another|
22
+
|[`memset`, `wmemset`](./reference/memset-wmemset.md)|Use given character to initialize specified number of bytes in the buffer|
23
+
|[`_swab`](./reference/swab.md)|Swap bytes of data and store them at specified location|
24
24
25
25
When the source and target areas overlap, only **memmove** is guaranteed to copy the full source properly.
Gets a character string from the console. More secure versions of these functions are available; see [_cgets_s, _cgetws_s](./reference/cgets-s-cgetws-s.md).
15
+
Gets a character string from the console. More secure versions of these functions are available; see [`_cgets_s`, `_cgetws_s`](./reference/cgets-s-cgetws-s.md).
16
16
17
17
> [!IMPORTANT]
18
-
> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT. The secure versions of these functions, _cgets_s and _cgetws_s, are still available. For information on these alternative functions, see [_cgets_s, _cgetws_s](./reference/cgets-s-cgetws-s.md).
18
+
> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT. The secure versions of these functions, _cgets_s and _cgetws_s, are still available. For information on these alternative functions, see [`_cgets_s`, `_cgetws_s`](./reference/cgets-s-cgetws-s.md).
19
19
20
20
> [!IMPORTANT]
21
21
> This API cannot be used in applications that execute in the Windows Runtime. For more information, see [CRT functions not supported in Universal Windows Platform apps](../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md).
|[_mbclen, mblen, _mblen_l](./reference/mbclen-mblen-mblen-l.md)|Return length of valid multibyte character; result depends on **LC_CTYPE** category setting of current locale|
|[`_mbclen`, `mblen`, `_mblen_l`](./reference/mbclen-mblen-mblen-l.md)|Return length of valid multibyte character; result depends on **LC_CTYPE** category setting of current locale|
Copy file name to clipboardExpand all lines: docs/c-runtime-library/code-pages.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ The Microsoft runtime library uses the following types of code pages:
22
22
23
23
also sets the locale to the system-default ANSI code page.
24
24
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).
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).
26
26
27
-
- 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.
27
+
- 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.
28
28
29
29
- The "C" locale is defined by ANSI to correspond to the locale in which C programs have traditionally executed. The code page for the "C" locale ("C" code page) corresponds to the ASCII character set. For example, in the "C" locale, **islower** returns true for the values 0x61 - 0x7A only. In another locale, **islower** may return `true` for these and other values, as defined by that locale.
Copy file name to clipboardExpand all lines: docs/c-runtime-library/commit-to-disk-constants.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ The commit-to-disk modes are as follows:
24
24
25
25
-**c**
26
26
27
-
Writes the unwritten contents of the specified buffer to disk. This commit-to-disk functionality only occurs at explicit calls to either the [fflush](./reference/fflush.md) or the [_flushall](./reference/flushall.md) function. This mode is useful when dealing with sensitive data. For example, if your program terminates after a call to `fflush` or `_flushall`, you can be sure that your data reached the operating system's buffers. However, unless a file is opened with the **c** option, the data might never make it to disk if the operating system also terminates.
27
+
Writes the unwritten contents of the specified buffer to disk. This commit-to-disk functionality only occurs at explicit calls to either the [`fflush`](./reference/fflush.md) or the [`_flushall`](./reference/flushall.md) function. This mode is useful when dealing with sensitive data. For example, if your program terminates after a call to `fflush` or `_flushall`, you can be sure that your data reached the operating system's buffers. However, unless a file is opened with the **c** option, the data might never make it to disk if the operating system also terminates.
28
28
29
29
-**n**
30
30
@@ -35,7 +35,7 @@ The commit-to-disk modes are as follows:
35
35
36
36
## Using the commit-to-disk feature with existing code
37
37
38
-
By default, calls to the [fflush](./reference/fflush.md) or [_flushall](./reference/flushall.md) library functions write data to buffers maintained by the operating system. The operating system determines the optimal time to actually write the data to disk. The commit-to-disk feature of the run-time library lets you ensure that critical data is written directly to disk rather than to the operating system's buffers. You can give this capability to an existing program without rewriting it by linking its object files with COMMODE.OBJ.
38
+
By default, calls to the [`fflush`](./reference/fflush.md) or [`_flushall`](./reference/flushall.md) library functions write data to buffers maintained by the operating system. The operating system determines the optimal time to actually write the data to disk. The commit-to-disk feature of the run-time library lets you ensure that critical data is written directly to disk rather than to the operating system's buffers. You can give this capability to an existing program without rewriting it by linking its object files with COMMODE.OBJ.
39
39
40
40
In the resulting executable file, calls to `fflush` write the contents of the buffer directly to disk, and calls to `_flushall` write the contents of all buffers to disk. These two functions are the only ones affected by COMMODE.OBJ.
41
41
@@ -44,6 +44,6 @@ In the resulting executable file, calls to `fflush` write the contents of the bu
0 commit comments