Part 2 of the POSIX changes

Author: Colin Robertson

.openpublishing.redirection.json

@@ -835,6 +835,16 @@
       "redirect_url": "/cpp/c-runtime-library/c-run-time-library-reference",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/c-runtime-library/inp-inpw.md",
+      "redirect_url": "/cpp/c-runtime-library/inp-inpw-inpd",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/c-runtime-library/outp-outpw.md",
+      "redirect_url": "/cpp/c-runtime-library/outp-outpw-outpd",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/c-runtime-library/precision-specification.md",
       "redirect_url": "/cpp/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions#precision",

docs/c-runtime-library/compatibility.md

@@ -1,27 +1,28 @@
 ---
 title: "Compatibility"
-ms.date: "11/04/2016"
+description: "Describes the compatibility of the Microsoft Universal C runtime library (UCRT) with the Standard C library, POSIX, the Safe CRT, and Store apps."
+ms.date: "12/06/2019"
 f1_keywords: ["c.programs"]
 helpviewer_keywords: ["CRT, compatibility", "compatibility, C run-time libraries", "compatibility"]
 ms.assetid: 346709cb-edda-4909-9a19-3d253eddb6b7
 ---
 # Compatibility
 
-The Universal C Run-Time Library (UCRT) supports most of the C standard library required for  C++ conformance. It implements the C99 (ISO/IEC 9899:1999)  library, with the exceptions of the type-generic macros defined in \<tgmath.h>, and strict type compatibility in \<complex.h>. The UCRT also implements a large subset of the POSIX.1 (ISO/IEC 9945-1:1996, the POSIX System Application Program Interface) C library, but is not fully conformant to any specific POSIX standard.  In addition, the UCRT implements several Microsoft-specific functions and macros that are not part of a standard.
+The Universal C Run-Time Library (UCRT) supports most of the C standard library required for  C++ conformance. It implements the C99 (ISO/IEC 9899:1999) library, with certain exceptions: The type-generic macros defined in \<tgmath.h>, and strict type compatibility in \<complex.h>. 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.
 
-Functions specific to the Microsoft implementation of Visual C++ are found in the vcruntime library.  Many of these functions are for internal use and cannot be called by user code. Some are documented for use in debugging and implementation compatibility.
+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.
 
-The C++ standard reserves names that begin with an underscore in the global namespace to the implementation. Because the POSIX functions are in the global namespace, but are not part of the standard C runtime library, the Microsoft-specific implementations of these functions have a leading underscore. For portability, the UCRT also supports the default names, but the Microsoft C++ compiler issues a deprecation warning when code that uses them is compiled. Only the default POSIX names are deprecated, not the functions. To suppress the warning, define `_CRT_NONSTDC_NO_WARNINGS` before including any headers in code that uses the original POSIX names.
+The C++ standard reserves names that begin with an underscore in the global namespace to the implementation. Both the POSIX functions and Microsoft-specific runtime library functions are in the global namespace, but aren't part of the standard C runtime library. That's why the preferred Microsoft implementations of these functions have a leading underscore. For portability, the UCRT also supports the default names, but the Microsoft C++ compiler issues a deprecation warning when code that uses them is compiled. Only the default names are deprecated, not the functions themselves. To suppress the warning, define `_CRT_NONSTDC_NO_WARNINGS` before including any headers in code that uses the original POSIX names.
 
-Certain functions in the standard C library have a history of unsafe usage, because of misused parameters and unchecked buffers. These functions are often the source of security issues in code. Microsoft created a set of safer versions of these functions that verify parameter usage and invoke the invalid parameter handler when an issue is detected at runtime.  By default, the Microsoft C++ compiler issues a deprecation warning when a function is used that has a safer variant available. When you compile your code as C++ , you can define `_CRT_SECURE_CPP_OVERLOAD_STANDARD_NAMES` as 1 to eliminate most warnings. This uses template overloads to call the safer variants while maintaining portable source code. To suppress the warning, define `_CRT_SECURE_NO_WARNINGS` before including any headers in code that uses these functions. For more information, see [Security Features in the CRT](../c-runtime-library/security-features-in-the-crt.md).
+Certain functions in the standard C library have a history of unsafe usage, because of misused parameters and unchecked buffers. These functions are often the source of security issues in code. Microsoft created a set of safer versions of these functions that verify parameter usage. They invoke the invalid parameter handler when an issue is detected at runtime.  By default, the Microsoft C++ compiler issues a deprecation warning when a function is used that has a safer variant available. When you compile your code as C++, you can define `_CRT_SECURE_CPP_OVERLOAD_STANDARD_NAMES` as 1 to eliminate most warnings. This macro enables template overloads to call the safer variants while maintaining portable source code. To suppress the warning, define `_CRT_SECURE_NO_WARNINGS` before including any headers in code that uses these functions. For more information, see [Security Features in the CRT](../c-runtime-library/security-features-in-the-crt.md).
 
-Except as noted within the documentation for specific functions, the UCRT is compatible with the Windows API.  Certain functions are not supported in Windows 8 Store apps or in Universal Windows Platform (UWP) apps on Windows 10. These functions are listed in [CRT functions not supported in Universal Windows Platform apps](../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md), which enumerates the functions not supported by the Windows Runtime and [UWP](/uwp).
+Except as noted within the documentation for specific functions, the UCRT is compatible with the Windows API.  Certain functions aren't supported in Windows Store or Universal Windows Platform ([UWP](/uwp)) apps. These functions are listed in [CRT functions not supported in Universal Windows Platform apps](../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md).
 
 ## Related Articles
 
 |Title|Description|
 |-----------|-----------------|
-|[UWP Apps, the Windows Runtime, and the C Run-Time](../c-runtime-library/windows-store-apps-the-windows-runtime-and-the-c-run-time.md)|Describes when UCRT routines are not compatible with Universal Windows apps or Microsoft Store apps.|
+|[UWP Apps, the Windows Runtime, and the C Run-Time](../c-runtime-library/windows-store-apps-the-windows-runtime-and-the-c-run-time.md)|Describes when UCRT routines aren't compatible with Universal Windows apps or Microsoft Store apps.|
 |[ANSI C Compliance](../c-runtime-library/ansi-c-compliance.md)|Describes standard-compliant naming in the UCRT.|
 |[UNIX](../c-runtime-library/unix.md)|Provides guidelines for porting programs to UNIX.|
 |[Windows Platforms (CRT)](../c-runtime-library/windows-platforms-crt.md)|Lists the operating systems that are the CRT supports.|

docs/c-runtime-library/inp-inpw-inpd.md

@@ -1,27 +1,26 @@
 ---
-title: "_inp, _inpw, _inpd"
-ms.date: "11/04/2016"
-api_name: ["_inp", "_inpw", "_inpd"]
+title: "inp, _inp, inpw, _inpw, _inpd"
+description: "Describes the obsolete and removed inp, _inp, inpw, _inpw, and _inpd functions of the Microsoft C runtime library (CRT)."
+ms.date: "12/09/2019"
+api_name: ["inp", "inpw", "_inp", "_inpw", "_inpd"]
 api_location: ["msvcrt.dll", "msvcr120.dll", "msvcr110_clr0400.dll", "msvcr110.dll", "msvcr80.dll", "msvcr100.dll", "msvcr90.dll"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
-f1_keywords: ["inpd", "_inp", "_inpw", "_inpd"]
+f1_keywords: ["inp", "inpw", "_inp", "_inpw", "_inpd"]
 helpviewer_keywords: ["inp function", "inpw function", "ports, I/O routines", "inpd function", "_inp function", "_inpd function", "I/O [CRT], port", "_inpw function"]
 ms.assetid: 5d9c2e38-fc85-4294-86d5-7282cc02d1b3
 ---
-# _inp, _inpw, _inpd
+# inp, _inp, inpw, _inpw, _inpd
 
-Inputs, from a port, a byte (`_inp`), a word (`_inpw`), or a double word (`_inpd`).
+Inputs, from a port, a byte (`inp`, `_inp`), a word (`inpw`, `_inpw`), or a double word (`_inpd`).
 
 > [!IMPORTANT]
->  These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.
-
-> [!IMPORTANT]
->  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).
+> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.  
+> 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).
 
 ## Syntax
 
-```
+```cpp
 int _inp(
    unsigned short port
 );
@@ -33,9 +32,9 @@ unsigned long _inpd(
 );
 ```
 
-#### Parameters
+### Parameters
 
-*port*<br/>
+*port*\
 I/O port number.
 
 ## Return Value
@@ -48,6 +47,8 @@ The `_inp`, `_inpw`, and `_inpd` functions read a byte, a word, and a double wor
 
 Because these functions read directly from an I/O port, they cannot be used in user code.
 
+The `inp` and `inpw` names are older, deprecated names for the `_inp` and `_inpw` functions. For more information, see [POSIX function names](../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md#posix-function-names).
+
 ## Requirements
 
 |Routine|Required header|
@@ -64,5 +65,5 @@ All versions of the [C run-time libraries](../c-runtime-library/crt-library-feat
 
 ## See also
 
-[Console and Port I/O](../c-runtime-library/console-and-port-i-o.md)<br/>
-[_outp, _outpw, _outpd](../c-runtime-library/outp-outpw-outpd.md)
+[Console and Port I/O](../c-runtime-library/console-and-port-i-o.md)\
+[outp, outpw, _outp, _outpw, _outpd](../c-runtime-library/outp-outpw-outpd.md)

docs/c-runtime-library/inp-inpw.md

@@ -1,6 +1,7 @@
 ---
-title: "Obsolete Functions"
-ms.date: "01/22/2019"
+title: "Obsolete functions"
+description: "Lists the obsolete functions that have been deprecated and removed from the Microsoft C runtime library (CRT)."
+ms.date: "12/09/2019"
 api_name: ["_beep", "_sleep", "_loaddll", "_getdllprocaddr", "_seterrormode", "is_wctype", "_getsystime", "_setsystime"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-process-l1-1-0.dll", "api-ms-win-crt-runtime-l1-1-0.dll", "api-ms-win-crt-string-l1-1-0.dll", "api-ms-win-crt-time-l1-1-0.dll"]
 api_type: ["DLLExport"]
@@ -11,7 +12,7 @@ ms.assetid: 8e14c2d4-1481-4240-8586-47eb43db02b0
 ---
 # Obsolete Functions
 
-Certain library functions are obsolete and have more recent equivalents. We recommend you change these to the updated versions. Other obsolete functions have been removed from the CRT. This topic lists the functions deprecated as obsolete, and the functions removed in a particular version of Visual Studio.
+Certain library functions are obsolete and have more recent equivalents. We recommend you change these functions to the updated versions. Other obsolete functions have been removed from the CRT. This article lists the functions deprecated as obsolete, and the functions removed in a particular version of Visual Studio.
 
 ## Deprecated as obsolete in Visual Studio 2015
 
@@ -36,14 +37,12 @@ Certain library functions are obsolete and have more recent equivalents. We reco
 |[_get_output_format](../c-runtime-library/get-output-format.md)|None|
 |[_heapadd](../c-runtime-library/heapadd.md)|None|
 |[_heapset](../c-runtime-library/heapset.md)|None|
-|[inp, inpw](../c-runtime-library/inp-inpw.md)|None|
-|[_inp, _inpw, _inpd](../c-runtime-library/inp-inpw-inpd.md)|None|
-|[outp, outpw](../c-runtime-library/outp-outpw.md)|None|
-|[_outp, _outpw, _outpd](../c-runtime-library/outp-outpw-outpd.md)|None|
+|[inp, inpw, _inp, _inpw, _inpd](../c-runtime-library/inp-inpw-inpd.md)|None|
+|[outp, outpw, _outp, _outpw, _outpd](../c-runtime-library/outp-outpw-outpd.md)|None|
 |[_set_output_format](../c-runtime-library/set-output-format.md)|None|
 
 ## Removed from the CRT in earlier versions of Visual Studio
 
 [_lock](../c-runtime-library/lock.md)
 
-[_unlock](../c-runtime-library/unlock.md)
+[_unlock](../c-runtime-library/unlock.md)

docs/c-runtime-library/obsolete-functions.md

@@ -1,47 +1,46 @@
 ---
-title: "_outp, _outpw, _outpd"
-ms.date: "11/04/2016"
-api_name: ["_outpd", "_outp", "_outpw"]
+title: "outp, outpw, _outp, _outpw, _outpd"
+description: "Describes the obsolete and removed outp, outpw, _outp, _outpw, and _outpd functions of the Microsoft C runtime library (CRT)."
+ms.date: "12/09/2019"
+api_name: ["_outpd", "_outp", "_outpw", "outp", "outpw"]
 api_location: ["msvcrt.dll", "msvcr100.dll", "msvcr120.dll", "msvcr90.dll", "msvcr110_clr0400.dll", "msvcr110.dll", "msvcr80.dll"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
-f1_keywords: ["_outpw", "_outpd", "_outp", "outpd"]
+f1_keywords: ["_outpw", "_outpd", "_outp", "outp", "outpw", "outpd"]
 helpviewer_keywords: ["outpw function", "words", "_outpd function", "outpd function", "outp function", "ports, writing bytes at", "bytes, writing to ports", "words, writing to ports", "double words", "double words, writing to ports", "_outpw function", "_outp function"]
 ms.assetid: c200fe22-41f6-46fd-b0be-ebb805b35181
 ---
-# _outp, _outpw, _outpd
+# outp, outpw, _outp, _outpw, _outpd
 
-Outputs, at a port, a byte (`_outp`), a word (`_outpw`), or a double word (`_outpd`).
+Outputs, at a port, a byte (`outp`, `_outp`), a word (`outpw`, `_outpw`), or a double word (`_outpd`).
 
 > [!IMPORTANT]
->  These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.
-
-> [!IMPORTANT]
->  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).
+> These functions are obsolete. Beginning in Visual Studio 2015, they are not available in the CRT.  
+> 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).
 
 ## Syntax
 
-```
-
-      int _outp(
-unsigned short port,
-int databyte
+```cpp
+int _outp(
+   unsigned short port,
+   int databyte
 );
 unsigned short _outpw(
-unsigned short port,
-unsigned short dataword
+   unsigned short port,
+   unsigned short dataword
 );
 unsigned long _outpd(
-unsigned short port,
-unsigned long dataword
+   unsigned short port,
+   unsigned long dataword
 );
 ```
 
-#### Parameters
-*port*<br/>
+### Parameters
+
+*port*\
 Port number.
 
-*databyte, dataword*<br/>
+*databyte, dataword*\
 Output values.
 
 ## Return Value
@@ -54,6 +53,8 @@ The `_outp`, `_outpw`, and `_outpd` functions write a byte, a word, and a double
 
 Because these functions write directly to an I/O port, they cannot be used in user code. For information about using I/O ports in these operating systems, search for "Serial Communications in Win32" at MSDN.
 
+The `outp` and `outpw` names are older, deprecated names for the `_outp` and `_outpw` functions. For more information, see [POSIX function names](../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md#posix-function-names).
+
 ## Requirements
 
 |Routine|Required header|
@@ -70,5 +71,5 @@ All versions of the [C run-time libraries](../c-runtime-library/crt-library-feat
 
 ## See also
 
-[Console and Port I/O](../c-runtime-library/console-and-port-i-o.md)<br/>
-[_inp, _inpw, _inpd](../c-runtime-library/inp-inpw-inpd.md)
+[Console and Port I/O](../c-runtime-library/console-and-port-i-o.md)\
+[inp, inpw, _inp, _inpw, _inpd](../c-runtime-library/inp-inpw-inpd.md)