Long.parseLong, Double.parseDouble, Integer.parseInt are too lenient about gwt HOT 15 CLOSED

Reported by gwt.team.scottb on 2006-09-15 19:01:17

from gwt.

I happened to run into this bug earlier today, and did a quick fix saying if the
length of the returned number is not equal to the length of the input string then
dont return the number, although I'm sure there is an better way!

Reported by james.crow on 2006-12-12 23:55:33

from gwt.

If the number is a negative number, the suggested quick fix won't work. Same if the
string had a unary +

Reported by grprakash on 2006-12-14 14:36:04

from gwt.

Shunting this your way.  The right answer may very well be that it's acceptable for
our parsing functions to be more lenient in web mode for the sake of efficiency.

Reported by gwt.team.scottb on 2006-12-15 19:31:59

from gwt.

Reported by gwt.team.hcc on 2006-12-21 17:07:08

from gwt.

Isn't this already fixed?

Reported by gwt.team.bruce on 2007-01-22 21:34:11

• Status changed: NeedsInfo
• Labels added: Category-JRE

from gwt.

It's fixed pending code review...

Reported by gwt.team.hcc on 2007-02-21 18:22:08

from gwt.

I have the same problem in version 1.3.3 for Long.parseLong. Has this fix made it to
a public version?

Reported by wboyle on 2007-03-26 16:28:14

from gwt.

I'm also seeing this problem with GWT 1.3.3 for parseDouble.

Reported by wpietri on 2007-03-30 02:17:40

from gwt.

This has been addressed as part of issue 915.

Reported by gwt.team.bobv on 2007-04-19 21:45:51

• Status changed: Duplicate

from gwt.

Reported by galgwt.reviews on 2008-11-06 18:28:18

• Labels added: Status-Fixed

from gwt.

Reported by galgwt.reviews on 2008-11-06 18:31:17

• Labels removed: Status-Fixed

from gwt.

The problem is there in GWT v1.7.1

Reported by onderuzun on 2012-04-05 16:38:27

from gwt.

Looking at test cases we have in emul this seems to be solved

from gwt.

FWIW, I believe that was fixed in b87cd06 (apparently shipped in 1.4.10 or something like that (we don't have all tags for those very old releases)); there's been a few commits afterwards to actually loosen the validation: 884c189, efa7a10, b96f11a, 2a1d511; or fix edge cases (e.g. 625967f)

from gwt.