Bug 17628 - "55" (or "\xFF15\xFF15") is recognized as an integer
Summary: "55" (or "\xFF15\xFF15") is recognized as an integer
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 3.2.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
Depends on:
Reported: 2014-02-05 18:39 UTC by Gustavo Guerra
Modified: 2014-02-14 11:37 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Gustavo Guerra 2014-02-05 18:39:09 UTC
This was caught on the FSharp.Data unit tests running on Travis with

.NET doesn't consider it as an integer, Mono parses it as 717783. It should either stick with .NET behaviour, or at least parse it as 55
Comment 1 Miguel de Icaza [MSFT] 2014-02-11 17:47:49 UTC
Can you please tell us which method has this bug?
Comment 2 Gustavo Guerra 2014-02-11 17:53:30 UTC
int.TryParse("55", NumberStyles.Integer, CultureInfo.InvariantCulture) reproduces it (but I assume int.Parse, and all long, decimal, etc variations might also have the same problem)

Found here: 
Comment 3 Marek Safar 2014-02-14 11:37:35 UTC
Fixed in master