Skip to content

Commit 5187996

Browse files
mikeblomeColin Robertson
mikeblome
authored and
Colin Robertson
committed
link fixes across vcppdocs (#84)
* fixed broken link in high level nav page * various broken links in cpp folder * link fixed * link fixes in cpp lang docs * more link fixes * link fixes in concrt * fixed codecvt-* filenames * link fixes in atl * link fixes in atl-mfc-shared * link fixes in data/odbc casing still not fixed * fixed links to members in mfc * fixed casing in link paths * moved top files back into top * more link fixes * links in high level TOC to restore links to top, plus misc other fixes * fixed build error and misc links * more link fixes * Fix missed merge issue * Fix another merge issue. * misc link fixes * Fix merge conflict issues
1 parent 4366b13 commit 5187996

1,187 files changed

Lines changed: 5322 additions & 4998 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/_breadcrumb/toc.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
items:
99
- name: Documentation
1010
tocHref: /cpp/
11-
topicHref: /cpp/top/visual-cpp-in-visual-studio
11+
topicHref: /cpp/visual-cpp-in-visual-studio
1212
items:
1313
- name: C++ Language
1414
tocHref: /cpp/cpp/

‎docs/assembler/masm/microsoft-macro-assembler-reference.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The Microsoft Macro Assembler (MASM) provides several advantages over inline ass
6161
Information about how to create output files for [!INCLUDE[vcprx64](../../assembler/inline/includes/vcprx64_md.md)].
6262

6363
## Related Sections
64-
[Visual C++](../../top/visual-cpp-in-visual-studio.md)
64+
[Visual C++](../../visual-cpp-in-visual-studio.md)
6565
Provides links to different areas of the Visual Studio and Visual C++ documentation.
6666

6767
[Visual C++ Reference](http://msdn.microsoft.com/en-us/1ba03b5c-8229-4f63-b08c-6c12141d6ab1)

‎docs/atl-mfc-shared/TOC.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,4 +29,4 @@
2929
#### [CString Exception Cleanup](cstring-exception-cleanup.md)
3030
#### [CString Argument Passing](cstring-argument-passing.md)
3131
#### [Unicode and Multibyte Character Set (MBCS) Support](unicode-and-multibyte-character-set-mbcs-support.md)
32-
# [Reference](reference/TOC.md)
32+
# [Reference](reference/toc.md)

‎docs/atl-mfc-shared/allocating-and-releasing-memory-for-a-bstr.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -46,19 +46,19 @@ When you create `BSTR`s and pass them between COM objects, you must take care in
4646

4747
- When you call into a function that expects a `BSTR` argument, you must allocate the memory for the `BSTR` before the call and release it afterwards. For example:
4848

49-
[!code-cpp[NVC_ATLMFC_Utilities#192](../atl-mfc-shared/codesnippet/CPP/allocating-and-releasing-memory-for-a-bstr_1.cpp)]
49+
[!code-cpp[NVC_ATLMFC_Utilities#192](../atl-mfc-shared/codesnippet/cpp/allocating-and-releasing-memory-for-a-bstr_1.cpp)]
5050

51-
[!code-cpp[NVC_ATLMFC_Utilities#193](../atl-mfc-shared/codesnippet/CPP/allocating-and-releasing-memory-for-a-bstr_2.cpp)]
51+
[!code-cpp[NVC_ATLMFC_Utilities#193](../atl-mfc-shared/codesnippet/cpp/allocating-and-releasing-memory-for-a-bstr_2.cpp)]
5252

5353
- When you call into a function that returns a `BSTR`, you must free the string yourself. For example:
5454

55-
[!code-cpp[NVC_ATLMFC_Utilities#194](../atl-mfc-shared/codesnippet/CPP/allocating-and-releasing-memory-for-a-bstr_3.cpp)]
55+
[!code-cpp[NVC_ATLMFC_Utilities#194](../atl-mfc-shared/codesnippet/cpp/allocating-and-releasing-memory-for-a-bstr_3.cpp)]
5656

57-
[!code-cpp[NVC_ATLMFC_Utilities#195](../atl-mfc-shared/codesnippet/CPP/allocating-and-releasing-memory-for-a-bstr_4.cpp)]
57+
[!code-cpp[NVC_ATLMFC_Utilities#195](../atl-mfc-shared/codesnippet/cpp/allocating-and-releasing-memory-for-a-bstr_4.cpp)]
5858

5959
- When you implement a function that returns a `BSTR`, allocate the string but do not free it. The receiving the function releases the memory. For example:
6060

61-
[!code-cpp[NVC_ATLMFC_Utilities#196](../atl-mfc-shared/codesnippet/CPP/allocating-and-releasing-memory-for-a-bstr_5.cpp)]
61+
[!code-cpp[NVC_ATLMFC_Utilities#196](../atl-mfc-shared/codesnippet/cpp/allocating-and-releasing-memory-for-a-bstr_5.cpp)]
6262

6363
## See Also
6464
[Strings (ATL/MFC)](../atl-mfc-shared/strings-atl-mfc.md)

‎docs/atl-mfc-shared/avoidance-of-heap-contention.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The default string managers provided by MFC and ATL are simple wrappers on top o
4242
## Example
4343
The example below illustrates a thread procedure that allocates its own private non-thread-safe heap to use for strings on that thread:
4444

45-
[!code-cpp[NVC_ATLMFC_Utilities#182](../atl-mfc-shared/codesnippet/CPP/avoidance-of-heap-contention_1.cpp)]
45+
[!code-cpp[NVC_ATLMFC_Utilities#182](../atl-mfc-shared/codesnippet/cpp/avoidance-of-heap-contention_1.cpp)]
4646

4747
## Comments
4848
Multiple threads could be running using this same thread procedure but since each thread has its own heap there is no contention between threads. In addition, the fact that each heap is not thread-safe gives a measurable increase in performance even if just one copy of the thread is running. This is the result of the heap not using expensive interlocked operations to protect against concurrent access.

‎docs/atl-mfc-shared/basic-cstring-operations.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,11 @@ This topic explains the following basic [CString](../atl-mfc-shared/reference/cs
6363

6464
- Assign the value of a C literal string to a `CString` object.
6565

66-
[!code-cpp[NVC_ATLMFC_Utilities#183](../atl-mfc-shared/codesnippet/CPP/basic-cstring-operations_1.cpp)]
66+
[!code-cpp[NVC_ATLMFC_Utilities#183](../atl-mfc-shared/codesnippet/cpp/basic-cstring-operations_1.cpp)]
6767

6868
- Assign the value of one `CString` to another `CString` object.
6969

70-
[!code-cpp[NVC_ATLMFC_Utilities#184](../atl-mfc-shared/codesnippet/CPP/basic-cstring-operations_2.cpp)]
70+
[!code-cpp[NVC_ATLMFC_Utilities#184](../atl-mfc-shared/codesnippet/cpp/basic-cstring-operations_2.cpp)]
7171

7272
The contents of a `CString` object are copied when one `CString` object is assigned to another. Therefore, the two strings do not share a reference to the actual characters that make up the string. For more information about how to use `CString` objects as values, see [CString Semantics](../atl-mfc-shared/cstring-semantics.md).
7373

@@ -80,7 +80,7 @@ This topic explains the following basic [CString](../atl-mfc-shared/reference/cs
8080
## <a name="_core_concatenating_two_cstring_objects"></a> Concatenating Two CString Objects
8181
To concatenate two `CString` objects, use the concatenation operators (+ or +=), as follows.
8282

83-
[!code-cpp[NVC_ATLMFC_Utilities#185](../atl-mfc-shared/codesnippet/CPP/basic-cstring-operations_3.cpp)]
83+
[!code-cpp[NVC_ATLMFC_Utilities#185](../atl-mfc-shared/codesnippet/cpp/basic-cstring-operations_3.cpp)]
8484

8585
At least one argument to the concatenation operators (+ or +=) must be a `CString` object, but you can use a constant character string (for example, `"big"`) or a `char` (for example, 'x') for the other argument.
8686

@@ -97,7 +97,7 @@ This topic explains the following basic [CString](../atl-mfc-shared/reference/cs
9797

9898
The `CStringT` class template defines the relational operators (<, \<=, >=, >, ==, and !=), which are available for use by `CString`. You can compare two `CStrings` by using these operators, as shown in the following example.
9999

100-
[!code-cpp[NVC_ATLMFC_Utilities#186](../atl-mfc-shared/codesnippet/CPP/basic-cstring-operations_4.cpp)]
100+
[!code-cpp[NVC_ATLMFC_Utilities#186](../atl-mfc-shared/codesnippet/cpp/basic-cstring-operations_4.cpp)]
101101

102102
## <a name="_core_converting_cstring_objects"></a> Converting CString Objects
103103
For information about converting CString objects to other string types, see [How to: Convert Between Various String Types](../text/how-to-convert-between-various-string-types.md).

‎docs/atl-mfc-shared/cstring-argument-passing.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,9 @@ This article explains how to pass [CString](../atl-mfc-shared/reference/cstringt
5555
## <a name="_core_strings_as_function_outputs"></a> Strings as Function Outputs
5656
Typically you can return `CString` objects from functions because `CString` objects follow value semantics like primitive types. To return a read-only string, use a constant `CString` reference (**const CString&**). The following example illustrates the use of `CString` parameters and return types:
5757

58-
[!code-cpp[NVC_ATLMFC_Utilities#197](../atl-mfc-shared/codesnippet/CPP/cstring-argument-passing_1.cpp)]
58+
[!code-cpp[NVC_ATLMFC_Utilities#197](../atl-mfc-shared/codesnippet/cpp/cstring-argument-passing_1.cpp)]
5959

60-
[!code-cpp[NVC_ATLMFC_Utilities#198](../atl-mfc-shared/codesnippet/CPP/cstring-argument-passing_2.cpp)]
60+
[!code-cpp[NVC_ATLMFC_Utilities#198](../atl-mfc-shared/codesnippet/cpp/cstring-argument-passing_2.cpp)]
6161

6262
## See Also
6363
[Strings (ATL/MFC)](../atl-mfc-shared/strings-atl-mfc.md)

‎docs/atl-mfc-shared/cstring-operations-relating-to-c-style-strings.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ strcpy(myString, (LPCTSTR)aCString);
7373

7474
Sometimes you may require a copy of `CString` data to modify directly. Use the more secured function `strcpy_s` (or the Unicode/MBCS-portable `_tcscpy_s`) to copy the `CString` object into a separate buffer. This is where characters can be safely modified, as shown by the following example.
7575

76-
[!code-cpp[NVC_ATLMFC_Utilities#189](../atl-mfc-shared/codesnippet/CPP/cstring-operations-relating-to-c-style-strings_1.cpp)]
76+
[!code-cpp[NVC_ATLMFC_Utilities#189](../atl-mfc-shared/codesnippet/cpp/cstring-operations-relating-to-c-style-strings_1.cpp)]
7777

7878
> [!NOTE]
7979
> The third argument to `strcpy_s` (or the Unicode/MBCS-portable `_tcscpy_s`) is either a `const``wchar_t*` (Unicode) or a `const``char*` (ANSI). The example above passes a `CString` for this argument. The C++ compiler automatically applies the conversion function defined for the `CString` class that converts a `CString` to an `LPCTSTR`. The ability to define casting operations from one type to another is one of the most useful features of C++.
@@ -103,14 +103,14 @@ strcpy(myString, (LPCTSTR)aCString);
103103

104104
To use a `CString` object in a variable argument function, explicitly cast the `CString` to an `LPCTSTR` string, as shown in the following example.
105105

106-
[!code-cpp[NVC_ATLMFC_Utilities#190](../atl-mfc-shared/codesnippet/CPP/cstring-operations-relating-to-c-style-strings_2.cpp)]
106+
[!code-cpp[NVC_ATLMFC_Utilities#190](../atl-mfc-shared/codesnippet/cpp/cstring-operations-relating-to-c-style-strings_2.cpp)]
107107

108108
## <a name="_core_specifying_cstring_formal_parameters"></a> Specifying CString Formal Parameters
109109
For most functions that need a string argument, it is best to specify the formal parameter in the function prototype as a `const` pointer to a character (`LPCTSTR`) instead of a `CString`. When a formal parameter is specified as a `const` pointer to a character, you can pass either a pointer to a `TCHAR` array, a literal string [`"hi there"`], or a `CString` object. The `CString` object will be automatically converted to an `LPCTSTR`. Any place you can use an `LPCTSTR`, you can also use a `CString` object.
110110

111111
You can also specify a formal parameter as a constant string reference (that is, `const``CString&`) if the argument will not be modified. Drop the `const` modifier if the string will be modified by the function. If a default null value is desired, initialize it to the null string [`""`], as shown below:
112112

113-
[!code-cpp[NVC_ATLMFC_Utilities#191](../atl-mfc-shared/codesnippet/CPP/cstring-operations-relating-to-c-style-strings_3.cpp)]
113+
[!code-cpp[NVC_ATLMFC_Utilities#191](../atl-mfc-shared/codesnippet/cpp/cstring-operations-relating-to-c-style-strings_3.cpp)]
114114

115115
For most function results, you can simply return a `CString` object by value.
116116

‎docs/atl-mfc-shared/cstring-semantics.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Even though [CString](../atl-mfc-shared/reference/cstringt-class.md) objects are
3939

4040
You can assign one **CString** object to another. However, when you modify one of the two `CString` objects, the other `CString` object is not modified, as shown by the following example:
4141

42-
[!code-cpp[NVC_ATLMFC_Utilities#188](../atl-mfc-shared/codesnippet/CPP/cstring-semantics_1.cpp)]
42+
[!code-cpp[NVC_ATLMFC_Utilities#188](../atl-mfc-shared/codesnippet/cpp/cstring-semantics_1.cpp)]
4343

4444
Note in the example that the two `CString` objects are considered "equal" because they represent the same character string. The `CString` class overloads the equality operator (`==`) to compare two `CString` objects based on their value (contents) rather than their identity (address).
4545

‎docs/atl-mfc-shared/current-time-automation-classes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The following procedure shows how to create a `COleDateTime` object and initiali
4545

4646
2. Call `GetCurrentTime`.
4747

48-
[!code-cpp[NVC_ATLMFC_Utilities#177](../atl-mfc-shared/codesnippet/CPP/current-time-automation-classes_1.cpp)]
48+
[!code-cpp[NVC_ATLMFC_Utilities#177](../atl-mfc-shared/codesnippet/cpp/current-time-automation-classes_1.cpp)]
4949

5050
## See Also
5151
[Date and Time: Automation Support](../atl-mfc-shared/date-and-time-automation-support.md)

0 commit comments

Comments
 (0)