Bug 25295 - Numeric data types issues using Parse
Summary: Numeric data types issues using Parse
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2014-12-11 12:36 UTC by Caronte
Modified: 2015-01-12 08:20 UTC (History)
2 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 Caronte 2014-12-11 12:36:16 UTC
When i try to overflow a int data type using int.Parse, this doesn't happen.

System.UInt32 x = System.UInt32.MaxValue + System.UInt32.Parse("1");
int y = int.MaxValue + int.Parse("1");

//returns 0

short.MaxValue implicity converts short type to int.

short x = short.MaxValue - short.Parse("1");

// returns Error CS0266.

I think that there are more problems with doubles, decimals, etc, too.

Please, excuse me my english.

Comment 1 Marek Safar 2015-01-12 08:20:39 UTC
that's expected because it's running un unchecked context.

You probably want to do instead something like

System.UInt32 x = checked (System.UInt32.MaxValue + System.UInt32.Parse("1"));