Skip to content

Commit c885074

Browse files
JasonCardJasonCard
authored
proposed workaround to address loc issue
@corob-msft This is the proposed workaround to address [https://github.com/MicrosoftDocs/cpp-docs.de-de/issues/62](https://github.com/MicrosoftDocs/cpp-docs.de-de/issues/62). We found that for some reason the double quotation marks in the following lines within the code block (lines 57 - 69) are causing this issue for our loc transformer: ``` cout << "unsigned val = " << num << " signed val = " << num2 << endl; … cout << "unsigned val = " << num << " signed val = " << num2 << endl; ``` However, this transformer will be replaced with a new one next FY, so unfortunately we won’t be dedicating any dev resource to fix it. As a workaround, we found that adding double quotation marks after those lines above, for example in line 62 and 68 like below, would resolve the issue, but could that be considered? // Prints: “unsigned val = 65535 signed val = -1”
1 parent 660abf4 commit c885074

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎docs/cpp/type-conversions-and-type-safety-modern-cpp.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,13 +59,13 @@ using namespace std;
5959
unsigned short num = numeric_limits<unsigned short>::max(); // #include <limits>
6060
short num2 = num;
6161
cout << "unsigned val = " << num << " signed val = " << num2 << endl;
62-
// Prints: unsigned val = 65535 signed val = -1
62+
// Prints: "unsigned val = 65535 signed val = -1"
6363

6464
// Go the other way.
6565
num2 = -1;
6666
num = num2;
6767
cout << "unsigned val = " << num << " signed val = " << num2 << endl;
68-
// Prints: unsigned val = 65535 signed val = -1
68+
// Prints: "unsigned val = 65535 signed val = -1"
6969
```
7070

7171
Notice that values are reinterpreted in both directions. If your program produces odd results in which the sign of the value seems inverted from what you expect, look for implicit conversions between signed and unsigned integral types. In the following example, the result of the expression ( 0 - 1) is implicitly converted from **`int`** to **`unsigned int`** when it's stored in `num`. This causes the bit pattern to be reinterpreted.

0 commit comments

Comments
 (0)