summaryrefslogtreecommitdiff
path: root/xmlsecurity/source/helper/xsecparser.hxx
diff options
context:
space:
mode:
authorEike Rathke <erack@redhat.com>2024-05-14 22:59:28 +0200
committerEike Rathke <erack@redhat.com>2024-05-15 18:02:19 +0200
commit1ea85e8f2d815e6c0834215714ed3dad1101b971 (patch)
treeb99cdcf3312c35776db9d6fcec3629a762974a23 /xmlsecurity/source/helper/xsecparser.hxx
parent045a21f08abff10592fe303abf0f311a83777e81 (diff)
Resolves: tdf#160985 Max integer representation for rtl_math_StringFormat_G
Same as for rtl_math_StringFormat_Automatic we want to preserve the highest accuracy of integer values also with rtl_math_StringFormat_G if nDecPlaces is large enough, instead of possibly rounding into 15 digits. This occurred with FastSaxSerializer::write(double) but rtl::OString::number(double) and rtl::OUString::number(double) and rtl_math_doubleToString() and rtl::str::valueOfFP() and rtl_str_valueOfDouble() and all places calling with rtl_math_StringFormat_G are similar affected. Question might remain why those places use rtl_math_StringFormat_G with fixed nDecimalPlaces calculated from RTL_STR_MAX_VALUEOFDOUBLE - SAL_N_ELEMENTS("-x.E-xxx") + 1 instead of rtl_math_StringFormat_Automatic with rtl_math_DecimalPlaces_Max. Change-Id: Ib388b119faed441c9020dca803649a4089da5b07 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167647 Tested-by: Jenkins Reviewed-by: Eike Rathke <erack@redhat.com>
Diffstat (limited to 'xmlsecurity/source/helper/xsecparser.hxx')
0 files changed, 0 insertions, 0 deletions