Skip to content

Commit 0513794

Browse files
TylerMSFTTylerMSFT
authored andcommitted
test formatting fix
1 parent 18b3a51 commit 0513794

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

docs/c-runtime-library/reference/cprintf-p-cprintf-p-l-cwprintf-p-cwprintf-p-l.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,7 @@ Also, like **_cprintf_s** and **_cwprintf_s**, they validate the input pointer a
6767
> [!IMPORTANT]
6868
> Ensure that *format* is not a user-defined string.
6969
>
70+
>
7071
> Starting in Windows 10 version 2004 (build 19041), the `printf` family of functions prints exactly representable floating point numbers according to the IEEE 754 rules for rounding. In previous versions of Windows, exactly representable floating point numbers ending in '5' would always round up. IEEE 754 states that they must round to the closest even digit (also known as "Banker's Rounding"). For example, both `printf("%1.0f", 1.5)` and `printf("%1.0f", 2.5)` should round to 2. Previously, 1.5 would round to 2 and 2.5 would round to 3. This change only affects exactly representable numbers. For example, 2.35 (which, when represented in memory, is closer to 2.35000000000000008) continues to round up to 2.4. Rounding done by these functions now also respects the floating point rounding mode set by [`fesetround`](fegetround-fesetround2.md). Previously, rounding always chose `FE_TONEAREST` behavior. This change only affects programs built using Visual Studio 2019 version 16.2 and later. To use the legacy floating point rounding behavior, link with [`legacy_stdio_float_rounding.obj`](../link-options.md).
7172
7273
### Generic-Text Routine Mappings

0 commit comments

Comments
 (0)