|author||John Layt <email@example.com>||2011-08-25 07:54:16 +0100|
|committer||Qt by Nokia <firstname.lastname@example.org>||2012-02-05 00:26:07 +0100|
QDateTime: Store Julian Day as qint64
Store the QDate Julian Day number as an qint64 instead of uint32 to enable support for dates before 2 January 4713 BCE. This changes the possible date range to be approx 2.5 Quadrillion BC to 2.5 Quadrillion AD. A qint32 was not used as it only covers 5 million BCE to 5 million CE which does include Geological or Astronomical time. The effective supported date range is currently 4800 BCE to 1.4 million CE due to restrictions in existing conversion formulas. The effective range will be extended later with new formulas. Change-Id: Ib4345369455b31d4edae8c933b7721e76414e914 Reviewed-by: Thiago Macieira <email@example.com>
Diffstat (limited to 'dist')
1 files changed, 6 insertions, 0 deletions
diff --git a/dist/changes-5.0.0 b/dist/changes-5.0.0
index 8e1f6e3575..ed5ddc240d 100644
@@ -247,6 +247,12 @@ QtCore
0 and QDate::shortMonthName() will return QString().
* Adding days to a null QDate or seconds to a null QTime will no longer return
a valid QDate/QTime.
+ * QDate stores the Julian Day as a qint64 extending date support across a
+ more interesting range, see the class documentation for details.
+ * Conversion to YMD form dates is only accurate between to 4800 BCE to
+ 1.4 million CE
+ * The QDate::addDays() and QDateTime::addDays() methods now take a qint64
+ * The QDate::daysTo() and QDateTime::daysTo() methods now return a qint64
* QIntValidator and QDoubleValidator no longer fall back to using the C locale if