Update keywords through __ptr64 for synonyms

Author: Colin Robertson

docs/assembler/inline/asm.md

@@ -1,10 +1,10 @@
 ---
 title: "__asm | Microsoft Docs"
 ms.custom: ""
-ms.date: "08/30/2018"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-masm"]
 ms.topic: "conceptual"
-f1_keywords: ["__asm", "__asm_cpp"]
+f1_keywords: ["__asm", "_asm", "__asm_cpp"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__asm keyword [C++], vs. asm blocks", "__asm keyword [C++]"]
 ms.assetid: 77ff3bc9-a492-4b5e-85e1-fa4e414e79cd
@@ -47,6 +47,8 @@ did not cause native code to be generated when compiled with **/clr**; the compi
 
 `__asm int 3` now results in native code generation for the function. If you want a function to cause a break point in your code and if you want that function compiled to MSIL, use [__debugbreak](../../intrinsics/debugbreak.md).
 
+For compatibility with previous versions, **_asm** is a synonym for **__asm** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ## Example
 
 The following code fragment is a simple `__asm` block enclosed in braces:

docs/cpp/alignof-operator.md

@@ -1,10 +1,10 @@
 ---
 title: "__alignof Operator | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["alignas_cpp", "__alignof_cpp", "alignof_cpp"]
+f1_keywords: ["alignas_cpp", "__alignof_cpp", "alignof_cpp", "__alignof", "_alignof"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["alignas [C++]", "alignment of structures", "__alignof keyword [C++]", "alignof [C++]", "types [C++], alignment requirements"]
 ms.assetid: acb1eed7-6398-40bd-b0c5-684ceb64afbc
@@ -65,6 +65,8 @@ int n = 50; // array size
 S* p = (S*)aligned_malloc(n * sizeof(S), __alignof(S));
 ```
 
+For compatibility with previous versions, **_alignof** is a synonym for **__alignof** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 For more information on modifying alignment, see:
 
 - [pack](../preprocessor/pack.md)

docs/cpp/based-pointers-cpp.md

@@ -1,10 +1,10 @@
 ---
 title: "Based Pointers (C++) | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__based", "__based_cpp"]
+f1_keywords: ["__based", "_based", "__based_cpp"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__based keyword [C++]", "based pointers", "pointers, based"]
 ms.assetid: 1e5f2e96-c52e-4738-8e14-87278681205e
@@ -48,7 +48,7 @@ The pointer `vpBuffer` is assigned the address of memory allocated at some later
 
 When dereferencing a based pointer, the base must be either explicitly specified or implicitly known through the declaration.
 
-For compatibility with previous versions, **_based** is a synonym for **__based**.
+For compatibility with previous versions, **_based** is a synonym for **__based** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
 
 ## Example
 

docs/cpp/cdecl.md

@@ -4,7 +4,7 @@ ms.custom: ""
 ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__cdecl_cpp", "__cdecl", "_cdecl" ]
+f1_keywords: ["__cdecl_cpp", "__cdecl", "_cdecl", "cdecl"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__cdecl keyword [C++]"]
 ms.assetid: 1ff1d03e-fb4e-4562-8be1-74f1ad6427f1
@@ -52,7 +52,7 @@ is equivalent to this:
 void __cdecl CMyClass::mymethod() { return; }
 ```
 
-For compatibility with previous versions, **_cdecl** is a synonym for **__cdecl** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+For compatibility with previous versions, **cdecl** and **_cdecl** are a synonym for **__cdecl** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
 
 ## Example
 

docs/cpp/declspec.md

@@ -1,10 +1,10 @@
 ---
 title: "__declspec | Microsoft Docs"
 ms.custom: ""
-ms.date: "1/23/2018"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__declspec_cpp"]
+f1_keywords: ["__declspec_cpp", "__declspec", "_declspec"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__declspec keyword [C++]"]
 author: "mikeblome"
@@ -56,6 +56,8 @@ Extended attribute grammar supports these Microsoft-specific storage-class attri
 
 The **code_seg**, **dllexport**, **dllimport**, **naked**, **noalias**, **nothrow**, **property**, **restrict**, **selectany**, **thread**, and **uuid** storage-class attributes are properties only of the declaration of the object or function to which they are applied. The **thread** attribute affects data and objects only. The **naked** and **spectre** attributes affect functions only. The **dllimport** and **dllexport** attributes affect functions, data, and objects. The **property**, **selectany**, and **uuid** attributes affect COM objects.
 
+For compatibility with previous versions, **_declspec** is a synonym for **__declspec** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 The **__declspec** keywords should be placed at the beginning of a simple declaration. The compiler ignores, without warning, any **__declspec** keywords placed after * or & and in front of the variable identifier in a declaration.
 
 A **__declspec** attribute specified in the beginning of a user-defined type declaration applies to the variable of that type. For example:

docs/cpp/fastcall.md

@@ -1,10 +1,10 @@
 ---
 title: "__fastcall | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__fastcall_cpp"]
+f1_keywords: ["__fastcall_cpp", "__fastcall", "_fastcall"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__fastcall keyword [C++]"]
 ms.assetid: bb5b9c8a-dfad-450c-9119-0ac2bc59544f
@@ -52,6 +52,8 @@ is equivalent to this:
 void __fastcall CMyClass::mymethod() { return; }
 ```
 
+For compatibility with previous versions, **_fastcall** is a synonym for **__fastcall** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ## Example
 
 In the following example, the function `DeleteAggrWrapper` is passed arguments in registers:

docs/cpp/inheritance-keywords.md

@@ -61,6 +61,8 @@ regardless of command-line options or pragmas, pointers to members of `class S`
 > [!NOTE]
 >  The same forward declaration of a class pointer-to-member representation should occur in every translation unit that declares pointers to members of that class, and the declaration should occur before the pointers to members are declared.
 
+For compatibility with previous versions, **_single_inheritance**, **_multiple_inheritance**, and **_virtual_inheritance** are synonyms for **__single_inheritance**, **__multiple_inheritance**, and **__virtual_inheritance** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 **END Microsoft Specific**
 
 ## See also

docs/cpp/inline-functions-cpp.md

@@ -1,10 +1,10 @@
 ---
 title: "Inline Functions (C++) | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__forceinline_cpp", "__inline_cpp", "inline_cpp"]
+f1_keywords: ["__forceinline_cpp", "__inline_cpp", "inline_cpp", "__inline", "_inline", "__forceinline", "_forceinline"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["inline functions [C++], class members"]
 ms.assetid: 355f120c-2847-4608-ac04-8dda18ffe10c
@@ -71,7 +71,7 @@ Using inline functions can make your program faster because they eliminate the o
 
 The compiler treats the inline expansion options and keywords as suggestions. There is no guarantee that functions will be inlined. You cannot force the compiler to inline a particular function, even with the **__forceinline** keyword. When compiling with **/clr**, the compiler will not inline a function if there are security attributes applied to the function.
 
-The **inline** keyword is available only in C++. The **__inline** and **__forceinline** keywords are available in both C and C++. For compatibility with previous versions, **_inline** is a synonym for **__inline** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+The **inline** keyword is available only in C++. The **__inline** and **__forceinline** keywords are available in both C and C++. For compatibility with previous versions, **_inline** and **_forceinline** are synonyms for **__inline**, and **__forceinline** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
 
 The **inline** keyword tells the compiler that inline expansion is preferred. However, the compiler can create a separate instance of the function (instantiate) and create standard calling linkages instead of inserting the code inline. Two cases where this can happen are:
 

docs/cpp/int8-int16-int32-int64.md

@@ -1,10 +1,10 @@
 ---
 title: "__int8, __int16, __int32, __int64 | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__int8_cpp", "__int16_cpp", "__int32_cpp", "__int64_cpp"]
+f1_keywords: ["__int8_cpp", "__int16_cpp", "__int32_cpp", "__int64_cpp", "__int8", "__int16", "__int32", "__int64", "_int8", "_int16", "_int32", "_int64"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__int16 keyword [C++]", "integer data type [C++], integer types in C++", "__int32 keyword [C++]", "integer types [C++]", "__int8 keyword [C++]", "__int64 keyword [C++]"]
 ms.assetid: 8e384602-2578-4980-8cc8-da63842356b2
@@ -29,6 +29,8 @@ __int64 nHuge;      // Declares 64-bit integer
 
 The types **__int8**, **__int16**, and **__int32** are synonyms for the ANSI types that have the same size, and are useful for writing portable code that behaves identically across multiple platforms. The **__int8** data type is synonymous with type **char**, **__int16** is synonymous with type **short**, and **__int32** is synonymous with type **int**. The **__int64** type is synonymous with type **long long**.
 
+For compatibility with previous versions, **_int8**, **_int16**, **_int32**, and **_int64** are synonyms for **__int8**, **__int16**, **__int32**, and **__int64** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ## Example
 
 The following sample shows that an __int*xx* parameter will be promoted to **int**:

docs/cpp/keywords-cpp.md

@@ -17,7 +17,7 @@ Keywords are predefined reserved identifiers that have special meanings. They ca
 
 |||||
 |-|-|-|-|
-|[__abstract](../dotnet/declaration-of-a-managed-class-type.md) <sup>2</sup>|[__alignof Operator](alignof-operator.md) <sup>4</sup>|[__asm](../assembler/inline/asm.md)<sup>4</sup>|[__assume](../intrinsics/assume.md) <sup>4</sup>|
+|[__abstract](../dotnet/declaration-of-a-managed-class-type.md) <sup>2</sup>|[__alignof Operator](alignof-operator.md) <sup>4</sup>|[__asm](../assembler/inline/asm.md) <sup>4</sup>|[__assume](../intrinsics/assume.md) <sup>4</sup>|
 |[__based](based-pointers-cpp.md) <sup>4</sup>|[__box](../dotnet/value-type-semantics.md) <sup>2</sup>|[__cdecl](cdecl.md) <sup>4</sup>|[__declspec](declspec.md) <sup>4</sup>|
 |[__delegate](../dotnet/delegates-and-events.md) <sup>2</sup>|[__event](event.md)|[__except](try-except-statement.md) <sup>4</sup>|[__fastcall](fastcall.md) <sup>4</sup>|
 |[__finally](try-finally-statement.md) <sup>4</sup>|[__forceinline](inline-functions-cpp.md) <sup>4</sup>|[__gc](../dotnet/declaration-of-a-clr-reference-class-object.md) <sup>2</sup>|[__hook](hook.md) <sup>3</sup>|

docs/cpp/ptr32-ptr64.md

@@ -1,10 +1,10 @@
 ---
 title: "__ptr32, __ptr64 | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__ptr32_cpp", "__ptr64_cpp"]
+f1_keywords: ["__ptr32_cpp", "__ptr64_cpp", "__ptr32", "__ptr64", "_ptr32", "_ptr64"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__ptr64 keyword [C++]", "_ptr32 keyword [C++]", "ptr32 keyword [C++]", "ptr64 keyword [C++]", "_ptr64 keyword [C++]", "__ptr32 keyword [C++]"]
 ms.assetid: afb563d8-7458-4fe7-9c30-bd4b5385a59f
@@ -30,6 +30,8 @@ On a 32-bit system, a pointer declared with **__ptr64** is truncated to a 32-bit
 > [!NOTE]
 > You cannot use **__ptr32** or **__ptr64** when compiling with **/clr:pure**. Otherwise, Compiler Error C2472 will be generated. The **/clr:pure** and **/clr:safe** compiler options are deprecated in Visual Studio 2015 and unsupported in Visual Studio 2017.
 
+For compatibility with previous versions, **_ptr32** and **_ptr64** are synonyms for **__ptr32** and **__ptr64** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ## Example
 
 The following example shows how to declare and allocate pointers with the **__ptr32** and **__ptr64** keywords.

docs/cpp/try-except-statement.md

@@ -1,10 +1,10 @@
 ---
 title: "try-except Statement | Microsoft Docs"
 ms.custom: ""
-ms.date: "10/05/2018"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["_abnormal_termination_cpp", "_exception_code_cpp", "EXCEPTION_CONTINUE_SEARCH", "_exception_info", "__except", "EXCEPTION_CONTINUE_EXECUTION", "_exception_code", "__except_cpp", "_exception_info_cpp", "EXCEPTION_EXECUTE_HANDLER", "_abnormal_termination"]
+f1_keywords: ["_abnormal_termination_cpp", "_exception_code_cpp", "EXCEPTION_CONTINUE_SEARCH", "_exception_info", "__except", "_except" "EXCEPTION_CONTINUE_EXECUTION", "_exception_code", "__except_cpp", "_exception_info_cpp", "EXCEPTION_EXECUTE_HANDLER", "_abnormal_termination"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__try keyword [C++]", "EXCEPTION_CONTINUE_EXECUTION macro", "EXCEPTION_CONTINUE_SEARCH macro", "EXCEPTION_EXECUTE_HANDLER macro", "GetExceptionCode function", "try-catch keyword [C++], try-except keyword [C++]", "_exception_code keyword [C++]", "try-except keyword [C++]", "_exception_info keyword [C++]", "_abnormal_termination keyword [C++]"]
 ms.assetid: 30d60071-ea49-4bfb-a8e6-7a420de66381
@@ -60,6 +60,8 @@ Each application can have its own exception handler.
 
 It is not valid to jump into a **__try** statement, but valid to jump out of one. The exception handler is not called if a process is terminated in the middle of executing a **try-except** statement.
 
+For compatibility with previous versions, **_try**, **_except**, and **_leave** are synonyms for **__try**, **__except**, and **__leave** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ### The __leave Keyword
 
 The **__leave** keyword is valid only within the guarded section of a **try-except** statement, and its effect is to jump to the end of the guarded section. Execution continues at the first statement after the exception handler.

docs/cpp/try-finally-statement.md

@@ -1,10 +1,10 @@
 ---
 title: "try-finally Statement | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-language"]
 ms.topic: "language-reference"
-f1_keywords: ["__try", "__leave_cpp", "__leave", "__finally_cpp", "__try_cpp", "__finally"]
+f1_keywords: ["__try", "_try", "__leave_cpp", "__leave", "__finally_cpp", "__try_cpp", "__finally", "_finally"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__try keyword [C++]", "__finally keyword [C++]", "__leave keyword [C++]", "try-catch keyword [C++], try-finally keyword", "try-finally keyword [C++]", "__finally keyword [C++], try-finally statement syntax", "__leave keyword [C++], try-finally statement", "structured exception handling [C++], try-finally"]
 ms.assetid: 826e0347-ddfe-4f6e-a7bc-0398e0edc7c2
@@ -61,6 +61,8 @@ Order of Termination-Handler Execution
 > [!NOTE]
 >  The behavior of try-finally is different from some other languages that support the use of **finally**, such as C#.  A single **__try** may have either, but not both, of **__finally** and **__except**.  If both are to be used together, an outer try-except statement must enclose the inner try-finally statement.  The rules specifying when each block executes are also different.
 
+For compatibility with previous versions, **_try**, **_finally**, and **_leave** are synonyms for **__try**, **__finally**, and **__leave** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ## The __leave Keyword
 
 The **__leave** keyword is valid only within the guarded section of a **try-finally** statement, and its effect is to jump to the end of the guarded section. Execution continues at the first statement in the termination handler.

docs/intrinsics/assume.md

@@ -1,10 +1,10 @@
 ---
 title: "__assume | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/09/2018"
 ms.technology: ["cpp-tools"]
 ms.topic: "reference"
-f1_keywords: ["__assume", "__assume_cpp"]
+f1_keywords: ["__assume", "_assume", "__assume_cpp"]
 dev_langs: ["C++"]
 helpviewer_keywords: ["__assume keyword [C++]"]
 ms.assetid: d8565123-b132-44b1-8235-5a8c8bff85a7
@@ -46,6 +46,8 @@ Use `__assume` in an [ASSERT](../c-runtime-library/reference/assert-asserte-asse
 
 The `__assume(0)` statement is a special case. Use `__assume(0)` to indicate a code path that cannot be reached. The following example shows how to use `__assume(0)` to indicate that the default case of a switch statement cannot be reached. This shows the most typical use of `__assume(0)`.
 
+For compatibility with previous versions, **_assume** is a synonym for **__assume** unless compiler option [/Za \(Disable language extensions)](../build/reference/za-ze-disable-language-extensions.md) is specified.
+
 ## Requirements
 
 |Intrinsic|Architecture|