Skip to content

Commit 028ba9a

Browse files
authored
Add "Remarks" headings for warning references in range [C6401, C6999]
1 parent 2643b99 commit 028ba9a

File tree

22 files changed

+44
-24
lines changed

22 files changed

+44
-24
lines changed

docs/code-quality/c6500.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: bfc61ec1-8ac5-4465-a23c-91418fbc4552
1010

1111
> Invalid annotation: value for '*name*' property is invalid
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that a property value used in the annotation isn't valid. For example, it can occur if an incorrect level of dereference is used in the `Deref` property, or if you use a constant value that is larger than `size_t` for properties like `ElementSize`.
1919

2020
Code analysis name: `INVALID_ATTRIBUTE_PROPERTY`

docs/code-quality/c6501.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: f9e8b847-2516-4bbb-bb1c-c87cfbacf254
1010

1111
> Annotation conflict: '*name*' property conflicts with previously specified property
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates the presence of conflicting properties in the annotation. The warning typically occurs when multiple properties that serve similar purpose are used to annotate a parameter or return value. To correct the warning, you must choose the property that best addresses your need.
1919

2020
Code analysis name: `CONFLICTING_ATTRIBUTE_PROPERTY_VALUES`

docs/code-quality/c6503.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: a6212938-bef9-4830-becb-6baa70b53e97
1010

1111
> Invalid annotation: references and arrays may not be marked `Null=Yes` or `Null=Maybe`
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that `Null` property is incorrectly used on a reference or array type. A reference or array type holds the address of an object and must point to a valid object. Because reference and array types can't be null, you must correct the error by either removing the `Null` property or by setting the `Null` property value to `No`.
1919

2020
Code analysis name: `REFERENCES_CANT_BE_NULL`

docs/code-quality/c6504.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,10 @@ helpviewer_keywords: ["C6504"]
99

1010
> Invalid annotation: property may only be used on values of pointer, pointer-to-member, or array type
1111
12-
This warning indicates the use of a pointer-specific SAL annotation on a non-pointer data type.
13-
1412
## Remarks
1513

14+
This warning indicates the use of a pointer-specific SAL annotation on a non-pointer data type.
15+
1616
For more information about what data types are supported by properties, see [Annotation Properties](using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1717

1818
Code analysis name: `NULL_ON_NON_POINTER`

docs/code-quality/c6508.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: ac5b23c8-ab9e-481b-bc97-8404f0b63100
1010

1111
> Invalid annotation: write access is not allowed on const values
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that the Access property specified on a const parameter implies that it can be written to. For constant values, Access=Read is the only valid setting.
1919

2020
Code analysis name: `WRITE_ACCESS_ON_CONST`

docs/code-quality/c6511.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: 1a0ac213-c205-4fb1-9bc3-3dc7885329fa
1010

1111
> Invalid annotation: MustCheck property must be Yes or No
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates an invalid value for `MustCheck` property was specified. The only valid values for this property are: Yes and No.
1919

2020
Code analysis name: `MUSTCHECK_MAYBE`

docs/code-quality/c6513.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: b27780ac-b237-4b26-a796-68a920da73a3
1010

1111
> Invalid annotation: ElementSizeConst requires additional size properties
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that `ElementSizeConst` requires other properties that are missing from the annotation. Specifying `ElementSizeConst` alone doesn't provide any benefit to the analysis process. In addition to specifying `ElementSize`, other properties such as `ValidElementsConst` or `WritableElementsConst` must also be specified.
1919

2020
Code analysis name: `ELEMENT_SIZE_WITHOUT_BUFFER_SIZE`

docs/code-quality/c6516.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: 461078c8-18d4-49ca-80a2-a15736f429a0
1010

1111
> Invalid annotation: no properties specified for '*name*' attribute
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that either no property was specified in the attribute or the property that was specified is invalid; therefore, the attribute can't be considered complete.
1919

2020
Code analysis name: `NO_PROPERTIES_ON_ATTRIBUTE`

docs/code-quality/c6517.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: 96822155-8b2a-4699-980f-744afff84ca8
1010

1111
> Invalid annotation: 'SAL_readableTo' property may not be specified on buffers that are not readable: '*Parameter*'.
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that `SAL_readableTo` property doesn't have the required read access. You can't use this property to annotate a parameter without providing read access.
1919

2020
Code analysis name: `VALID_SIZE_ON_NON_READABLE_BUFFER`

docs/code-quality/c6522.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.assetid: ac482f63-b27f-4807-968a-1c449033d2dd
1010

1111
> Invalid size specification: expression must be of integral type: annotation '*annotation*' on function '*function*' '*parameter*'
1212
13+
## Remarks
14+
1315
> [!NOTE]
1416
> This warning occurs only in code that is using a deprecated version of the source-code annotation language (SAL). We recommend that you port your code to use the latest version of SAL. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1517
16-
## Remarks
17-
1818
This warning indicates that an integral type was expected, but an incorrect data type was used. You can use annotation properties that accept the size of a parameter in terms of another parameter, but you must use correct data type. For a list of annotation properties, see [Using SAL Annotations to reduce code defects](using-sal-annotations-to-reduce-c-cpp-code-defects.md).
1919

2020
Code analysis name: `INVALID_SIZE_STRING_TYPE`

0 commit comments

Comments
 (0)