1/5/2021 AM Publish (#4022)

* Clarify C4146 per VCSig list (#3923)

* Clarify C4146 per VCSig list

* Fix link issues.

* Update enable CMake Presets

* fix rel links

* fix github 3528

* acrolinx

* change order of example

* Add version info to NMAKE macro functions

* Bulk fix entity `&` part 3

* threshhold test

* Eliminate even more `&` entities

* Minimum Viable Phix

* Once more into the `&` breech

* Add Visual Studio 2022 Platform Toolset Version

* Add /fpcvt compiler option docs (#3886)

* Add /fpcvt compiler option docs

* Fix copypasta error

* Update fp conversion intrinsics, too.

* Replace deleted table row

* Acrolinx pass

* Fix TOC issues

* Add useful links to intrinsics

* Updates per John Morgan, plus acrolink

* Update version info

* Clean up rvalue reference article

* Fix to `/fpcvt` per John Morgan email

* Reformat WeakRef class document.

* Update Advanced prop page and C1107

* Remove unrelated change.

* Minimizing entity form of & (#3916)

* Initial pass minimizing on > entities (#3919)

* Initial pass on > entities

* Fix everything.

* Try without `<` entities in title/desc

* Clean up pass

* Update docs/atl-mfc-shared/reference/cfiletime-class.md

Co-authored-by: Tracey Torble <[email protected]>

* Update tn026-ddx-and-ddv-routines.md

`DoDialogExchange` -> `DoDataExchange`

* Fix incorrect import example

* github fix 3544

* GITHUB FIX FOR #3549

* Add UWP to list of unsupported ASAN features.

* Fix misnamed mt.exe options. Acrolinx all.

* Attempt fpcvt simplification per John Morgan.

* Fix cpp-docs 3546

* Address complaint in cpp-docs 3554 (#3950)

* Add section on CMake partial activation

* 17.1 Update warnings, fix cpp-docs 3563 (#3954)

* 17.1 Update warnings, fix cpp-docs 3563

* fix date

* Add `/Zc:externC` compiler option doc, fix 1594

* Tweaks.

* Fix links, header syntax issues

* Fix issues in XML Docs reference

* Make list match apparently intended style

* Fix broken link.

* Add docs for new check

Signed-off-by: Kyle Reed <[email protected]>

* fix toc

* remove .md from toc title

* Revert "Add docs for new linter check"

* update runtime spelling

* Bulk fix: remove HTML entities from yml headers (#3962)

* Style and content fixes in cpp language docs

* Changing confusing wording about C++ exceptions

* Bulk fix HTML entities in H1 (#3966)

* Fix lt-gt entity pairs

* Bulk fix of `&lt;`-`&gt;` pairs in H1 headings

* Oops, deleted initial `#`

* Fix two more H1 issues

* update with existing .openpublishing.publish.config.json

* C++ tutorial landing page, attempt 2

* Revert redirection of get-started index.yml file

* Fix typo

* Bulk fix `&lt;`, `&gt;`, and `.period;` entities

* operatoroperator

* `/hotpatch`: No jump to the first instruction

* Update Acrolinx for main branch

* Change learn about item type

* Add get started TOC

* fix over machine translation problems (#3977)

* fix over machine translation problems

* acrolinx and misses

* markdown fixes

Co-authored-by: TylerMSFT <[email protected]>

* Make the grammar bot happy

* Fix things that look like parameters. (#3978)

* Fix things that look like parameters.

* Acrolinxy

* Misc fixes

* Other fixes

* Fix typos

* Acrolinx some more

* [17.0] Update links to download Visual Studio (#3981)

* Update links to download Visual Studio

* Remove VS 2019 reference

* Address cpp-docs 3565

* Also cpp-docs 439

* cpp-docs 947

* cpp-docs 1002

* accuratized

* cpp-docs 1035

* Twhitney named modules (#3960)

* draft

* draft

* draft

* fix links

* cleanup

* added some more info

* add some see also references

* cleanup pass

* remove text about overloads

* tech review

* little better wording

* a little more word smithing

* fix link

* acrolinx

* readthrough pass

* Readthrough to test building the project

* acrolinx

* rename media file

Co-authored-by: TylerMSFT <[email protected]>

* cpp-docs 1305

* cpp-docs 1324

* address github issue #3524 and add code escape to prevent over machine translation

* missed a couple escapes

* couple more code escapes

* one more escape

* Address cpp-docs 3583: LNK1107 clarity

* Tweaks

* tweak formatting

* Expand on fix for cpp-docs 1035 (#3986)

* Expand of fix for cpp-docs 1035

* Mention overloads.

* Grammar and formatting fixes

* add summary of what will learn in module

* [17.1p2] Add docs for comparison/bitwise c++ linter check. (#3964)

* Revert "Revert "Add docs for new linter check""

This reverts commit e56971f.

* PR feedback

Signed-off-by: Kyle Reed <[email protected]>

* Update cmake-presets-vs.md

* Update cmake-presets-vs.md

* Switch http to https and fix broken links

* Acrolinx

* Style pass for the grammar checker bot

* Fix two incorrect conditions in the ARM packed exception handling

For the prologue, the distinction between `mov r11, sp` and
`add r11, sp, #xx` lies only in whether other registers are pushed
before R11 and LR in prologue instruction 2. (The condition
`R`==1 and `PF`==0 corresponds to no other registers pushed before
`r11`.) The `L` flag doesn't affect it (and the documentation explicit
says that when `C` is set, then `L` also must be set, thus `C`==1
and `L`==0 is tautological too).

This was correctly described in the textual form, but the conditions
in the table included one erronous case.

For the epilogue, when `Ret`!=0, the function doesn't return by
popping LR directly into PC, but with an explicit branch instruction
(10a or 10b). In this case, if `L`==1, the LR register is included
in the list of registers popped in instruction 8. If register
homing is used (`H`==1), then instruction 9a is used instead of 9b.

This case seemed to have been overlooked both in the textual
description and in the table.

Also, when prologue instruction form 3a is used, clarify that
it corresponds to the unwind code FB (narrow nop) only, that unwinding
such a prologue doesn't restore `sp` from `r11`.

Also fix a typo and clarify that encodings with C=1, L=0 are
invalid.

* Address cpp-docs 3588 error in link commands (#3996)

* Address cpp-docs 3588 error in link commands

* Update ms.date

* Acrolinx fixes to frontrun cpp-docs 3541

* Post-3541 acrolinx pass

* Update how-to-marshal-structures-using-cpp-interop.md

Change "=" into "-"

* Add _CountOneBits[64] to the ARM64 intrinsic doc

* Update .acrolinx-config.edn

update to reflect default branch name change

* Mark first code block as C++

Syntax highlighting did not work for the `using identifier = type;` block due to missing language information.

* Fixed grammatical error in allocator-class.md

"Constructing a container with a custom allocator provide control over allocation and freeing of that container's elements." -> "Constructing a container with a custom allocator provides control over allocation and freeing of that container's elements."

* Update d-using-the-schedule-clause.md

* Correct a word in the remarks of /DIRECTIVES.

The section is .drectve instead of .drective.

* std::is_standard_layout<Derived>

* Make meaning clearer

This makes the meaning clearer to me. The ". Or," seems like to strong of a separator for closely related phrases.

* Update value-types-modern-cpp.md

Commas to make the meaning clearer

* add missing usage of CopyChars

* update json examples (#4017)

* update json examples

* acrolinx

Co-authored-by: TylerMSFT <[email protected]>

* fix github issue #3600

* formatting cleanup and acrolinx

* Address cpp-docs issues 3601 3622 3626

Co-authored-by: opbld16 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: PRMerger16 <[email protected]>
Co-authored-by: Erika <[email protected]>
Co-authored-by: Laura Brenner <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: PRMerger18 <[email protected]>
Co-authored-by: PRMerger4 <[email protected]>
Co-authored-by: PRMerger6 <[email protected]>
Co-authored-by: MohammadHadi Attarieh <[email protected]>
Co-authored-by: PRMerger15 <[email protected]>
Co-authored-by: PRMerger10 <[email protected]>
Co-authored-by: Haig MacGregor <[email protected]>
Co-authored-by: Tracey Torble <[email protected]>
Co-authored-by: Waiting <[email protected]>
Co-authored-by: roxk <[email protected]>
Co-authored-by: Tyler Whitney <[email protected]>
Co-authored-by: branh <[email protected]>
Co-authored-by: John Ellison <[email protected]>
Co-authored-by: PRMerger8 <[email protected]>
Co-authored-by: PRMerger17 <[email protected]>
Co-authored-by: Sam Freed <[email protected]>
Co-authored-by: Colin Cooper <[email protected]>
Co-authored-by: Paula Miller <[email protected]>
Co-authored-by: Kyle Reed <[email protected]>
Co-authored-by: Hannes Harnisch <[email protected]>
Co-authored-by: Anna Huff <[email protected]>
Co-authored-by: Ying Hua <[email protected]>
Co-authored-by: Alex Guteniev <[email protected]>
Co-authored-by: Dennis Rea <[email protected]>
Co-authored-by: PRMerger3 <[email protected]>
Co-authored-by: PRMerger Service account 2 <[email protected]>
Co-authored-by: Jonathan Sweemer <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: Kristine Toliver <[email protected]>
Co-authored-by: AndreaLu <[email protected]>
Co-authored-by: Matt Gardner <[email protected]>
Co-authored-by: Sarah Vilaysom <[email protected]>
Co-authored-by: Matthias <[email protected]>
Co-authored-by: James Oswald <[email protected]>
Co-authored-by: Anton Curmanschii <[email protected]>
Co-authored-by: ROOOO <[email protected]>
Co-authored-by: luozhiya <[email protected]>
Co-authored-by: Zane Hitchcox <[email protected]>
Co-authored-by: Chris Ho <[email protected]>
Co-authored-by: PRMerger5 <[email protected]>

Author: 49 people

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

@@ -160,13 +160,21 @@ static void CopyChars(
     XCHAR* pchDest,
     const XCHAR* pchSrc,
     int nChars) throw();
+static void CopyChars(
+    XCHAR* pchDest,
+    size_t nDestLen,
+    const XCHAR* pchSrc,
+    int nChars) throw();
 ```
 
 #### Parameters
 
 *`pchDest`*<br/>
 A pointer to a character string.
 
+*`nDestLen`*<br/>
+Buffer size of *`pchDest`*
+
 *`pchSrc`*<br/>
 A pointer to a string containing the characters to be copied.
 

docs/build/reference/directives.md

@@ -14,7 +14,7 @@ ms.assetid: cb85d679-6d20-4244-ba0b-6f495228e970
 
 ## Remarks
 
-This option dumps the compiler-generated .drective section of an image.
+This option dumps the compiler-generated .drectve section of an image.
 
 Only the [/HEADERS](headers.md) DUMPBIN option is available for use on files produced with the [/GL](gl-whole-program-optimization.md) compiler option.
 

docs/build/reference/nmake-function-patsubst.md

@@ -49,7 +49,7 @@ $(patsubst %lo,Bye,Hello Hey Hi) # Evaluates to "Bye Hey Hi"
 # A wildcard can be used in the pattern without a wildcard in the replacement
 
 $(patsubst he%,_%_,Hello Hey Hi) # Evaluates to "Hello Hey Hi" - patsubst is case-sensitive, so no substitutions performed
-$(patsubst he%,_%_,Hello Hey Hi) # Evaluates to "_llo_ _y_ Hi" - patsubsti is case-insensitive
+$(patsubsti he%,_%_,Hello Hey Hi) # Evaluates to "_llo_ _y_ Hi" - patsubsti is case-insensitive
 
 # patsubsti is commonly used to change the file extensions of a list of files
 OBJ_FILES=$(patsubst %.c,%.obj,$(C_SOURCES)) $(patsubst %.cpp,%.obj,$(patsubst %.cxx,%.obj,$(CPP_SOURCES)))

docs/cpp/address-of-operator-amp.md

@@ -15,7 +15,7 @@ ms.assetid: 2828221a-15f6-4acc-87fe-25e34feebb88
 
 ## Remarks
 
-The unary address-of operator (**`&`**) returns the address of (that is, a pointer to) its operand. The operand of the address-of operator can be a function designator. Or, it can be an lvalue that refers to an object that's not a bit field.
+The unary address-of operator (**`&`**) returns the address of (that is, a pointer to) its operand. The operand of the address-of operator can be a function designator or an lvalue that refers to an object that's not a bit field.
 
 The address-of operator can only be applied to certain lvalue expressions: either to variables of fundamental, structure, class, or union types, or to subscripted array references. In these expressions, a constant expression (one that doesn't include the address-of operator) can be added to or subtracted from the address-of expression.
 

docs/cpp/aliases-and-typedefs-cpp.md

@@ -11,7 +11,7 @@ You can use an *alias declaration* to declare a name to use as a synonym for a p
 
 ## Syntax
 
-```
+```cpp
 using identifier = type;
 ```
 

docs/cpp/new-operator-cpp.md

@@ -65,7 +65,7 @@ The **`new`** operator can't be used to allocate a function, but it can be used
 
 ```cpp
 int (**p) () = new (int (*[7]) ());
-delete *p;
+delete p;
 ```
 
 If you use the operator **`new`** without any extra arguments, and compile with the [`/GX`](../build/reference/gx-enable-exception-handling.md), [`/EHa`](../build/reference/eh-exception-handling-model.md), or [`/EHs`](../build/reference/eh-exception-handling-model.md) option, the compiler generates code to call operator **`delete`** if the constructor throws an exception.

docs/cpp/trivial-standard-layout-and-pod-types.md

@@ -83,7 +83,7 @@ struct Base
    int j;
 };
 
-// std::is_standard_layout<<Derived> == false!
+// std::is_standard_layout<Derived> == false!
 struct Derived : public Base
 {
    int x;
@@ -99,7 +99,7 @@ struct Base
    void Foo() {}
 };
 
-// std::is_standard_layout<<Derived> == true
+// std::is_standard_layout<Derived> == true
 struct Derived : public Base
 {
    int x;

docs/cpp/value-types-modern-cpp.md

@@ -7,7 +7,7 @@ ms.assetid: f63bb62c-60da-40d5-ac14-4366608fe260
 ---
 # C++ classes as value types
 
-C++ classes are by default value types. They can be specified as reference types, which enable polymorphic behavior to support object-oriented programming. Value types are sometimes viewed from the perspective of memory and layout control, whereas reference types are about base classes and virtual functions for polymorphic purposes. By default, value types are copyable, which means there is always a copy constructor and a copy assignment operator. For reference types, you make the class non-copyable (disable the copy constructor and copy assignment operator) and use a virtual destructor, which supports their intended polymorphism. Value types are also about the contents, which, when they are copied, always give you two independent values that can be modified separately. Reference types are about identity - what kind of object is it? For this reason, "reference types" are also referred to as "polymorphic types".
+C++ classes are, by default, value types. They can be specified as reference types, which enable polymorphic behavior to support object-oriented programming. Value types are sometimes viewed from the perspective of memory and layout control, whereas reference types are about base classes and virtual functions for polymorphic purposes. By default, value types are copyable, which means there is always a copy constructor and a copy assignment operator. For reference types, you make the class non-copyable (disable the copy constructor and copy assignment operator) and use a virtual destructor, which supports their intended polymorphism. Value types are also about the contents, which, when they are copied, always give you two independent values that can be modified separately. Reference types are about identity - what kind of object is it? For this reason, "reference types" are also referred to as "polymorphic types".
 
 If you really want a reference-like type (base class, virtual functions), you need to explicitly disable copying, as shown in the `MyRefType` class in the following code.
 

docs/parallel/openmp/d-using-the-schedule-clause.md

@@ -22,7 +22,7 @@ When there are repeated references to the same objects, the choice of schedule f
 }
 ```
 
-In the remaining examples, it's assumed that memory access isn't the dominant consideration. Unless otherwise stated, that all threads receive comparable computational resources. In these cases, the choice of schedule for a `for` construct depends on all the shared work that's to be performed between the nearest preceding barrier and either the implied closing barrier or the nearest upcoming  barrier, if there's a `nowait` clause. For each kind of schedule, a short example shows how that schedule kind is likely to be the best choice. A brief discussion follows each example.
+In the remaining examples, it's assumed that memory access isn't the dominant consideration. Unless otherwise stated, it is assumed that all threads receive comparable computational resources. In these cases, the choice of schedule for a `for` construct depends on all the shared work that's to be performed between the nearest preceding barrier and either the implied closing barrier or the nearest upcoming  barrier, if there's a `nowait` clause. For each kind of schedule, a short example shows how that schedule kind is likely to be the best choice. A brief discussion follows each example.
 
 The `static` schedule is also appropriate for the simplest case, a parallel region containing a single `for` construct, with each iteration requiring the same amount of work.
 

docs/preprocessor/pragma-directives-and-the-pragma-keyword.md

@@ -131,7 +131,7 @@ return _hr; \
 
 `_Pragma` is similar to the Microsoft-specific [`__pragma`](#the-pragma-keyword) keyword. It was introduced into the C standard in C99, and the C++ standard in C++11. It's available in C only when you specify the [`/std:c11` or `/std:c17`](../build/reference/std-specify-language-standard-version.md) option. For C++, it's available in all **`/std`** modes, including the default.
 
-Unlike **`__pragma`**, **`_Pragma`** allows you to put pragma directives into a macro definition. The string literal should be what you would otherwise put following a **`#pragma`** statement. For example:
+Unlike **`#pragma`**, **`_Pragma`** allows you to put pragma directives into a macro definition. The string literal should be what you would otherwise put following a **`#pragma`** statement. For example:
 
 ```c
 #pragma message("the #pragma way")

docs/standard-library/allocator-class.md

@@ -24,7 +24,7 @@ The type of object for which storage is being allocated or deallocated.
 
 ## Remarks
 
-All the C++ Standard Library containers have a template parameter that defaults to `allocator`. Constructing a container with a custom allocator provide control over allocation and freeing of that container's elements.
+All the C++ Standard Library containers have a template parameter that defaults to `allocator`. Constructing a container with a custom allocator provides control over allocation and freeing of that container's elements.
 
 For example, an allocator object might allocate storage on a private heap or in shared memory, or it might optimize for small or large object sizes. It might also specify, through the type definitions it supplies, that elements be accessed through special accessor objects that manage shared memory, or perform automatic garbage collection. Hence, a class that allocates storage using an allocator object should use these types for declaring pointer and reference objects, as the containers in the C++ Standard Library do.