path: root/src/gui/painting/qdrawingprimitive_sse2_p.h
diff options
authorEdward Welbourne <>2021-07-27 17:51:57 +0200
committerEdward Welbourne <>2021-08-03 14:49:57 +0200
commitb61a6e2507dd362b9b0478fc3b06c9a8f4a2977a (patch)
treed72bf3082cf3496e6caf742fa942a0777b0dccf0 /src/gui/painting/qdrawingprimitive_sse2_p.h
parent11476e5403c0f0ed997f0ecc9e5a82501441a667 (diff)
Consolidate documentation of floating-point formatting codeHEADdev
Move the documentation of the format and precision parameters to QLocale::toString(double, char, int), reference it from various QString methods (instead of repeating there and referencing one of those from QLocale). Add brief first lines for various documentation comments. Mention the special handling of negative precision in the moved documentation. Mention QLocale::FloatingPointShortest, add its type to \sa lines of methods it affects. Change a comment on some code implementing its special treatment to make clear that it does apply to 'e' and 'f' formats, not only to 'g', even though it has no overt special handling in that code; and update docs to report the undocumented behavior the comment previously described. Document how infinity and NaN are represented. Be somewhat more consistent about single-quoting the format names where referred to and applying \c to character constants. Make clear what things are different between different methods using these parameters. Reference QString::number() from QByteArray's relevant methods, since they share its quirks. In the process, rename the format and precision parameters of relevant functions so they're consistently named, replacing a mixture of abbreviated forms. Pick-to: 6.2 Change-Id: I077521b30346000e4b4f6968a8e750e934f72937 Reviewed-by: MÃ¥rten Nordheim <>
Diffstat (limited to 'src/gui/painting/qdrawingprimitive_sse2_p.h')
0 files changed, 0 insertions, 0 deletions