[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug classpath/25651] New: GregorianCalendar should handle leap seconds
From: |
green at redhat dot com |
Subject: |
[Bug classpath/25651] New: GregorianCalendar should handle leap seconds |
Date: |
3 Jan 2006 14:16:13 -0000 |
GregorianCalendar.nonLeniencyCheck() ensures that the seconds field is between
0 and 59 (inclusive). However, this upper limit may hit 60 when we insert leap
seconds (as we did three days ago). glibc says that tm.tm_sec can contain a
value of 60. Perhaps we should change the 59 limit to 60.
Here's a nice article on leap seconds: http://en.wikipedia.org/wiki/Leap_second
--
Summary: GregorianCalendar should handle leap seconds
Product: classpath
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: classpath
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: green at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25651
- [Bug classpath/25651] New: GregorianCalendar should handle leap seconds,
green at redhat dot com <=