You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fix broken link to profiling tools
* Fix issue in code sample.
* Format fixes
* Add draft of retargeting doc
* Additions and formatting
* Figure out why example isn't appearing
* Add multi-targeting doc to TOC
* Another attempt at example fix
* Fix missing code attempt 3
* Experiment with language filter
* Clean up code block language tags
* Remove "C" from dev_langs tags
* Remove dev_langs "C" tag in preprocessor
* Remove "C" dev_langs tag in CRT
* Unify dev_langs tags in c-language docs
* Remove uneeded dev_langs tags
* Fix another set of dev_langs issues
* Fix code block formatting issues.
Copy file name to clipboardExpand all lines: docs/atl-mfc-shared/reference/cimage-class.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,7 +141,7 @@ class CImage
141
141
`CImage` cannot be selected into a new [CDC](../../mfc/reference/cdc-class.md). `CImage` creates its own **HDC** for the image. Because an `HBITMAP` can only be selected into one **HDC** at a time, the `HBITMAP` associated with the `CImage` cannot be selected into another **HDC**. If you need a `CDC`, retrieve the **HDC** from the `CImage` and give it to [CDC::FromHandle](../../mfc/reference/cdc-class.md#cdc__fromhandle.
The following example creates a 100x100 pixel bitmap, using 16 bits to encode each pixel. In a given 16-bit pixel, bits 0-3 encode the red component, bits 4-7 encode green, and bits 8-11 encode blue. The remaining 4 bits are unused.
Copy file name to clipboardExpand all lines: docs/atl-mfc-shared/reference/crect-class.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -384,7 +384,7 @@ void DeflateRect(int l, int t, int r, int b) throw();
384
384
The first two overloads deflate both pairs of opposite sides of `CRect` so that its total width is decreased by two times *x* (or `cx`) and its total height is decreased by two times *y* (or `cy`). The other two overloads deflate each side of `CRect` independently of the others.
> Both of the rectangles must be normalized or this function may fail. You can call [NormalizeRect](#normalizerect) to normalize the rectangles before calling this function.
The third overload returns a new `CRect` that is equal to `CRect` deflated by the number of units specifed in each member of the parameter. Note that this overload functions like [DeflateRect](#deflaterect), not [SubtractRect](#subtractrect).
> Both of the rectangles must be normalized or this function may fail. You can call [NormalizeRect](#normalizerect) to normalize the rectangles before calling this function.
1122
1122
1123
1123
### Example
1124
-
```cpp
1124
+
```cpp
1125
1125
CRect rect1(100, 0, 200, 300);
1126
1126
CRect rect2(0, 100, 300, 200);
1127
1127
CRect rect3;
@@ -1159,7 +1159,7 @@ rect2) const throw();
1159
1159
CRect rect2( 0, 100, 300, 200);
1160
1160
CRect rect3;
1161
1161
1162
-
```cpp
1162
+
```cpp
1163
1163
CRect rect1(100, 0, 200, 300);
1164
1164
CRect rect2(0, 100, 300, 200);
1165
1165
CRect rect3;
@@ -1242,7 +1242,7 @@ void SetRect(int x1, int y1, int x2, int y2) throw();
> Both of the rectangles must be normalized or this function may fail. You can call [NormalizeRect](#normalizerect) to normalize the rectangles before calling this function.
> Both of the rectangles must be normalized or this function may fail. You can call [NormalizeRect](#normalizerect) to normalize the rectangles before calling this function.
The following example demonstrates the use of `CSimpleStringT::CSimpleStringT` by using the ATL `typedef``CSimpleString`. `CSimpleString` is a commonly used specialization of the class template `CSimpleStringT`.
The following code is modeled after [CComObjectRootEx](ccomobjectrootex-class.md), and demonstrates `AutoCriticalSection` being used in a threading environment.
Copy file name to clipboardExpand all lines: docs/build/arm-exception-handling.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,7 +207,7 @@ Windows on ARM uses the same structured exception handling mechanism for asynchr
207
207
208
208
The .xdata record is designed so that it is possible to fetch the first 8 bytes and compute the full size of the record, not including the length of the variable-sized exception data that follows. This code snippet computes the record size:
Copy file name to clipboardExpand all lines: docs/build/reference/arch-x86.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,15 +70,13 @@ Specifies the architecture for code generation on x86. Also see [/arch (x64)](..
70
70
71
71
**/arch** and [/QIfist](../../build/reference/qifist-suppress-ftol.md) cannot be used on the same compiland. In particular, if you do not use `_controlfp` to modify the FP control word, then the run-time startup code sets the x87 FPU control word precision-control field to 53-bits. Therefore, every float and double operation in an expression uses a 53-bit significand and a 15-bit exponent. However, every SSE single-precision operation uses a 24-bit significand and an 8-bit exponent, and SSE2 double-precision operations use a 53-bit significand and an 11-bit exponent. For more information, see [_control87, _controlfp, \__control87_2](../../c-runtime-library/reference/control87-controlfp-control87-2.md). These differences are possible in one expression tree, but not in cases where a user assignment is involved after each subexpression. Consider the following:
72
72
73
-
```c
74
-
73
+
```cpp
75
74
r = f1 * f2 + d; // Different results are possible on SSE/SSE2.
76
75
```
77
76
78
-
Against:
79
-
80
-
```c
77
+
Compare:
81
78
79
+
```cpp
82
80
t = f1 * f2; // Do f1 * f2, round to the type of t.
83
81
r = t + d; // This should produce the same overall result
Copy file name to clipboardExpand all lines: docs/build/reference/fp-specify-floating-point-behavior.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ Specifies floating-point behavior in a source code file.
92
92
93
93
To control floating-point behavior by function, see the [float_control](../../preprocessor/float-control.md) pragma. This overrides the **/fp** compiler setting. We recommend you save and restore local floating-point behavior as good engineering practice:
0 commit comments