On 18/08/2014 22:12, Mike Duigou wrote:
On Aug 14 2014, at 06:39 , Alan Bateman <alan.bate...@oracle.com> wrote:
On 14/08/2014 14:23, Claes Redestad wrote:
How about methods only taking beginIndex? Integer.parseInt("x: 10000000", 3,
10)? I guess these could to be dropped
to avoid ambiguity and instead allow for variations where radix can be left out.
I think there are two alternatives to the current implementation:
- only keep parseInt(CharSequence s, int beginIndex, int endIndex, int radix)
That's my preference
Looking at the examples I agree that providing only this one method is probably
the least error prone option.
I think we mostly got agreement on net-dev to re-examine the newly
introduced methods. I've created JDK-8055032 to track it and I'm sure
Claes will pick it up once he gets back.
-Alan.
