Skip to content

Commit f594e04

Browse files
Tyler WhitneyTyler Whitney
authored andcommitted
tech review feedback
1 parent 5420678 commit f594e04

3 files changed

Lines changed: 9 additions & 8 deletions

File tree

‎docs/build/walkthrough-compile-a-c-program-on-the-command-line.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ You can use NMAKE and makefiles, or MSBuild and project files to configure and b
171171
172172
The C and C++ languages are similar, but not the same. The Microsoft C/C++ compiler (MSVC) uses a simple rule to determine which language to use when it compiles your code. By default, the MSVC compiler treats all files that end in .c as C source code, and all files that end in .cpp as C++ source code. To force the compiler to treat all files as C non-dependent of file name extension, use the [/TC](reference/tc-tp-tc-tp-specify-source-file-type.md) compiler option.
173173
174-
MSVC is compatible with the ISO C99 standard, but not strictly compliant. In most cases, portable C code will compile and run as expected. Visual C++ provides support for the changes in ISO C11/C17. To compile with C11/17 support, use the compiler flag `/std:c11` or `/std:c17`. Certain library functions and POSIX function names are deprecated by MSVC. The functions are supported, but the preferred names have changed. For more information, see [Security Features in the CRT](../c-runtime-library/security-features-in-the-crt.md) and [Compiler Warning (level 3) C4996](../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md).
174+
MSVC is compatible with the ISO C99 standard, but not strictly compliant. In most cases, portable C code will compile and run as expected. Visual C++ provides support for the changes in ISO C11/C17. To compile with C11/C17 support, use the compiler flag `/std:c11` or `/std:c17`. Certain library functions and POSIX function names are deprecated by MSVC. The functions are supported, but the preferred names have changed. For more information, see [Security Features in the CRT](../c-runtime-library/security-features-in-the-crt.md) and [Compiler Warning (level 3) C4996](../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md).
175175
176176
## See also
177177

‎docs/c-runtime-library/compatibility.md‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "Compatibility"
3-
description: "Describes the compatibility of the Microsoft Universal C run-time library (UCRT) with the Standard C library, POSIX, the Safe CRT, and Store apps."
4-
ms.date: "12/06/2019"
5-
helpviewer_keywords: ["CRT, compatibility", "compatibility, C run-time libraries", "compatibility"]
3+
description: "Describes the compatibility of the Microsoft Universal C runtime library (UCRT) with the Standard C library, POSIX, the Safe CRT, and Store apps."
4+
ms.date: "9/11/2020"
5+
helpviewer_keywords: ["CRT, compatibility", "compatibility, C runtime libraries", "compatibility"]
66
ms.assetid: 346709cb-edda-4909-9a19-3d253eddb6b7
77
---
88
# Compatibility
@@ -11,8 +11,9 @@ The Universal C Runtime Library (UCRT) supports most of the C standard library r
1111
- strict type compatibility in \<complex.h>.
1212
- `aligned_alloc`, which will probably not be implemented because the Windows operating system doesn't support aligned allocations. Use the non-standard `_aligned_malloc`, instead.
1313
- `strerrorlen_s`
14-
- stdatomic.h
15-
- threads.h
14+
- atomic support in \<stdatomic.h>
15+
- threading support in \<threads.h>
16+
1617
The UCRT also implements a large subset of the POSIX.1 (ISO/IEC 9945-1:1996, the POSIX System Application Program Interface) C library. However, it's not fully conformant to any specific POSIX standard. The UCRT also implements several Microsoft-specific functions and macros that aren't part of a standard.
1718

1819
Functions specific to the Microsoft implementation of Visual C++ are found in the vcruntime library. Many of these functions are for internal use and can't be called by user code. Some are documented for use in debugging and implementation compatibility.

‎docs/c-runtime-library/reference/realloc.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,12 @@ If there is not enough available memory to expand the block to the given size, t
3939

4040
If *size* is zero, then the block pointed to by *memblock* is freed; the return value is **NULL**, and *memblock* is left pointing at a freed block.
4141

42-
The return value points to a storage space that is guaranteed to be suitably aligned for storage of any type of object. To get a pointer to a type other than **`void`**, use a type cast on the return value.
42+
The return value points to a storage space that is suitably aligned for storage of any type of object. To get a pointer to a type other than **`void`**, use a type cast on the return value.
4343

4444
## Remarks
4545

4646
> [!NOTE]
47-
> **realloc** hasn't been updated to implement C17 behavior.
47+
> **realloc** hasn't been updated to implement C17 behavior because the new behavior isn't compatible with the Windows operating system.
4848
4949
The **realloc** function changes the size of an allocated memory block. The *memblock* argument points to the beginning of the memory block. If *memblock* is **NULL**, **realloc** behaves the same way as **malloc** and allocates a new block of *size* bytes. If *memblock* is not **NULL**, it should be a pointer returned by a previous call to **calloc**, **malloc**, or **realloc**.
5050

0 commit comments

Comments
 (0)