Skip to content

Commit fd05d5f

Browse files
author
Colin Robertson
committed
Fixup See Also and Parameter blocks
1 parent 1f1eedc commit fd05d5f

File tree

277 files changed

+758
-748
lines changed

Some content is hidden

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

277 files changed

+758
-748
lines changed

‎docs/build/aggregates-and-unions.md‎

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,16 +14,19 @@ ms.workload: ["cplusplus"]
1414
# Aggregates and Unions
1515
Other types, such as arrays, structs, and unions, have stricter alignment requirements that ensure consistent aggregate and union storage and data retrieval. Here are the definitions for array, structure, and union:
1616

17-
Array
18-
Contains an ordered group of adjacent data objects. Each object is called an element. All elements within an array have the same size and data type.
17+
- Array
18+
19+
Contains an ordered group of adjacent data objects. Each object is called an element. All elements within an array have the same size and data type.
1920

20-
Structure
21-
Contains an ordered group of data objects. Unlike the elements of an array, the data objects within a structure can have different data types and sizes. Each data object in a structure is called a member.
21+
- Structure
22+
23+
Contains an ordered group of data objects. Unlike the elements of an array, the data objects within a structure can have different data types and sizes. Each data object in a structure is called a member.
2224

23-
Union
24-
An object that holds any one of a set of named members. The members of the named set can be of any type. The storage allocated for a union is equal to the storage required for the largest member of that union, plus any padding required for alignment.
25+
- Union
26+
27+
An object that holds any one of a set of named members. The members of the named set can be of any type. The storage allocated for a union is equal to the storage required for the largest member of that union, plus any padding required for alignment.
2528

26-
The following table shows the strongly suggested alignment for the scalar members of unions and structures.
29+
The following table shows the strongly suggested alignment for the scalar members of unions and structures.
2730

2831
||||
2932
|-|-|-|

‎docs/build/arm-exception-handling.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -740,6 +740,5 @@ Function:
740740

741741
## See also
742742

743-
[Overview of ARM ABI Conventions](../build/overview-of-arm-abi-conventions.md)
743+
[Overview of ARM ABI Conventions](../build/overview-of-arm-abi-conventions.md)<br/>
744744
[Common Visual C++ ARM Migration Issues](../build/common-visual-cpp-arm-migration-issues.md)
745-

‎docs/build/arm64-exception-handling.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -627,5 +627,5 @@ Note: EpilogStart Index [4] points to the middle of Prolog unwind code (partiall
627627

628628
## See also
629629

630-
[Overview of ARM64 ABI conventions](arm64-windows-abi-conventions.md)
630+
[Overview of ARM64 ABI conventions](arm64-windows-abi-conventions.md)<br/>
631631
[ARM Exception Handling](../build/arm-exception-handling.md)

‎docs/build/arm64-windows-abi-conventions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -222,5 +222,5 @@ Note that the cycle counter here is a true cycle counter, not a wall clock, and
222222

223223
## See also
224224

225-
[Common Visual C++ ARM Migration Issues](../build/common-visual-cpp-arm-migration-issues.md)
225+
[Common Visual C++ ARM Migration Issues](../build/common-visual-cpp-arm-migration-issues.md)<br/>
226226
[ARM64 exception handling](../build/arm64-exception-handling.md)

‎docs/build/batch-mode-rules.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ ms.author: "corob"
1212
ms.workload: ["cplusplus"]
1313
---
1414
# Batch-Mode Rules
15+
1516
```
1617
{frompath}.fromext{topath}.toext::
1718
commands

‎docs/build/building-c-cpp-isolated-applications.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,5 @@ An isolated application depends only on side-by-side assemblies and binds to its
1717
When you build your native C/C++ application using Visual C++, by default the Visual Studio project system generates a manifest file that describes your application's dependencies on Visual C++ libraries. If these are the only dependencies your application has, then it becomes an isolated application as soon as it is rebuilt with Visual Studio. If your application is using other libraries at runtime, then you may need to rebuild those libraries as side-by-side assemblies following the steps described in [Building C/C++ Side-by-side Assemblies](../build/building-c-cpp-side-by-side-assemblies.md).
1818

1919
## See Also
20-
[Concepts of Isolated Applications and Side-by-side Assemblies](../build/concepts-of-isolated-applications-and-side-by-side-assemblies.md)
21-
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
20+
[Concepts of Isolated Applications and Side-by-side Assemblies](../build/concepts-of-isolated-applications-and-side-by-side-assemblies.md)<br/>
21+
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)

‎docs/build/building-c-cpp-side-by-side-assemblies.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,6 @@ A [side-by-side assembly](/windows/desktop/SbsCs/about-side-by-side-assemblies-)
2929
This change may allow deployment of corresponding DLLs as a [private assembly](/windows/desktop/Msi/private-assemblies) in an application local folder or as a [shared assembly](/windows/desktop/Msi/shared-assemblies) in the WinSxS assembly cache. Several steps have to be followed in order to achieve correct runtime behavior of this new assembly; they are described in [Guidelines for Creating Side-by-side Assemblies](/windows/desktop/SbsCs/guidelines-for-creating-side-by-side-assemblies). After an assembly is correctly authored it can deployed as either a shared or private assembly together with an application that depends on it. When installing side-by-side assemblies as a shared assembly, you may either follow the guidelines outlined in [Installing Win32 Assemblies for Side-by-Side Sharing on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-side-by-side-sharing-on-windows-xp) or use [merge modules](https://msdn.microsoft.com/library/windows/desktop/aa369820). When installing side-by-side assemblies as a private assembly, you may just copy the corresponding DLL, resources and assembly manifest as part of the installation process to the application local folder on the target computer, ensuring that this assembly can be found by the loader at runtime (see [Assembly Searching Sequence](/windows/desktop/SbsCs/assembly-searching-sequence)). Another way is to use [Windows Installer](/windows/desktop/Msi/windows-installer-portal) and follow the guidelines outlined in [Installing Win32 Assemblies for the Private Use of an Application on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-the-private-use-of-an-application-on-windows-xp).
3030

3131
## See Also
32-
[Deployment Examples](../ide/deployment-examples.md)
33-
[Building C/C++ Isolated Applications](../build/building-c-cpp-isolated-applications.md)
34-
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
32+
[Deployment Examples](../ide/deployment-examples.md)<br/>
33+
[Building C/C++ Isolated Applications](../build/building-c-cpp-isolated-applications.md)<br/>
34+
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)

‎docs/build/common-visual-cpp-64-bit-migration-issues.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,5 +39,5 @@ For more information, see:
3939

4040
## See Also
4141

42-
[Configure Visual C++ for 64-bit, x64 targets](../build/configuring-programs-for-64-bit-visual-cpp.md)
42+
[Configure Visual C++ for 64-bit, x64 targets](../build/configuring-programs-for-64-bit-visual-cpp.md)<br/>
4343
[Visual C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md)

‎docs/build/conflicts-with-the-x86-compiler.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,5 +22,5 @@ Data types that are larger than 4 bytes are not automatically aligned on the sta
2222
If you require more strict alignment, use `__declspec(align(N)) on your variable declarations`. This causes the compiler to dynamically align the stack to meet your specifications. However, dynamically adjusting the stack at run time may cause slower execution of your application.
2323

2424
## See Also
25-
[Types and Storage](../build/types-and-storage.md)
26-
[align](../cpp/align-cpp.md)
25+
[Types and Storage](../build/types-and-storage.md)<br/>
26+
[align](../cpp/align-cpp.md)

‎docs/build/creating-a-resource-only-dll.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,5 +47,5 @@ The application should call `FreeLibrary` when it is finished using the resource
4747

4848
## See Also
4949

50-
[Working with Resource Files](../windows/working-with-resource-files.md)
50+
[Working with Resource Files](../windows/working-with-resource-files.md)<br/>
5151
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

0 commit comments

Comments
 (0)