From 1e3833bed8a661ee8ae284188a23bd0ffc3bed85 Mon Sep 17 00:00:00 2001 From: John Layt Date: Sun, 22 Jan 2012 21:23:50 +0000 Subject: QString: Make convert to number methods only use C locale Ensure consistent conversions by not using the system default locale. Change-Id: I60db9fc4f465c0254f3213419e57d7879aaddd65 Reviewed-by: Thiago Macieira Reviewed-by: Lars Knoll --- dist/changes-5.0.0 | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'dist') diff --git a/dist/changes-5.0.0 b/dist/changes-5.0.0 index e5f57732ba..ea88471990 100644 --- a/dist/changes-5.0.0 +++ b/dist/changes-5.0.0 @@ -240,6 +240,12 @@ QtCore now return an empty QString, QStringRef or QByteArray respectively. in Qt 4 they returned a null QString or a null QStringRef. +* QString methods toLongLong(), toULongLong(), toLong(), toULong(), toInt(), + toUInt(), toShort(), toUShort(), toDouble(), and toFloat() no longer use the + default or system locale, they will always use the C locale. This is to + guarantee consistent default conversion of strings. For locale-aware conversions + use the equivalent QLocale methods. + * QDate, QTime, and QDateTime have undergone important behavioural changes: * QDate only implements the Gregorian calendar, the switch to the Julian calendar before 1582 has been removed. This means all QDate methods will -- cgit v1.2.3