JDK-8076441 : Dead code in java.time.chrono.Chronology.isLeapYear after fixing JDK-8067800
- Type: Bug
- Component: core-libs
- Sub-Component: java.time
- Affected Version: 9
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-04-01
- Updated: 2016-06-13
- Resolved: 2015-04-02
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b59Fixed  |
Related Reports
|
Relates :
|
Description
The assignment to epochMonth in java/time/chrono/HijrahChronology.java is a dead code. It happened after following fix https://bugs.openjdk.java.net/browse/JDK-8067800
public boolean isLeapYear(long prolepticYear) {
checkCalendarInit();
if (prolepticYear < getMinimumYear() || prolepticYear > getMaximumYear()) {
return false;
}
int epochMonth = yearToEpochMonth((int) prolepticYear);
int len = getYearLength((int) prolepticYear);
return (len > 354);
}