Skip to content

Commit 25f764b

Browse files
committed
More review feedback
1 parent cab6b02 commit 25f764b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/code-quality/c6059.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: "Learn more about: Warning C6059"
33
title: Warning C6059
4-
ms.date: 10/04/2022
4+
ms.date: 12/14/2023
55
f1_keywords: ["C6059", "BAD_CONCATENATION", "__WARNING_BAD_CONCATENATION"]
66
helpviewer_keywords: ["C6059"]
77
ms.assetid: 343a4cd1-048a-4edf-bb4b-187097bb6093
@@ -81,7 +81,7 @@ void f( )
8181
8282
This analysis detects when the target buffer size is passed unmodified into the length parameter of the string manipulation function. The analysis is also able to detect cases where after simple computations the buffer size is passed as the length parameter. This warning isn't given if some other value is passed as the length parameter, even if that value is incorrect.
8383
84-
For example, let's consider the first example again. The following code generates warning C6059:
84+
Consider the following code, generates warning C6059:
8585
8686
```cpp
8787
#include <string.h>
@@ -100,7 +100,7 @@ void f( )
100100
}
101101
```
102102

103-
If we make a small change, changing the `MAX` argument to `strncat` to `MAX - 1`, the warning goes away, even though the length calculation is still incorrect.
103+
The warning goes away by changing the `MAX` argument to `strncat` to `MAX - 1`, even though the length calculation is still incorrect.
104104

105105
```cpp
106106
#include <string.h>

0 commit comments

Comments
 (0)