3167b157cd
Two examples were given, one to show "invalid" usage that would, in fact, work now - producing a date in 2012 - and the other to show "correct" code which, while correctly delivering the date in 1912 its author appears to have meant (albeit, giving a four-digit year would have made that clearer), uses the string API where code should normally construct dates - much more efficiently - by just passing the numbers to suitable constructors. Add tests verifying that the two date-times from the out-of-date examples do in fact work, even if you tell them the wrong century as default for two-digit dates. Pick-to: 6.7 6.5 Change-Id: I8155af019c80729323ba3958fe3942a72bfefc22 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 82d85c16d912b25bfa5b0a081e515fcecda1f975) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| qcalendar | ||
| qdate | ||
| qdatetime | ||
| qdatetimeparser | ||
| qtime | ||
| qtimezone | ||
| CMakeLists.txt | ||