JDK-8055251 : Re-examine Integer.parseInt and Long.parseLong methods
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-08-16
  • Updated: 2017-05-17
  • Resolved: 2014-09-10
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.
9 b31Fixed
Related Reports
Relates :  
The parseInt and parseLong methods introduced by JDK-8041972 are error prone due to the sequence of parameters with the same type and the ordering. This bug requests that these methods be re-examined. Specifically:

1. Consider dropping parseInt/parseLong(CharSequence, int radix, int beginIndex). It's not clear that there is a strong use-case for these methods.

2. Change the ordering of parseInt/parseLong(CharSequence, int radix, int beginIndex, int endIndex) so that the begin/endIndex are after the CS, the radix at the end.
For background on this topic, see this net-dev thread: http://mail.openjdk.java.net/pipermail/net-dev/2014-August/008625.html