[Mono-bugs] [Bug 72221][Nor] Changed - double tryparse with hex numbers returns opposite of .net

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=72221

--- shadow/72221	2005-02-11 00:44:22.000000000 -0500
+++ shadow/72221.tmp.30902	2005-12-12 15:09:37.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 72221
 Product: Mono: Class Libraries
 Version: 1.0
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: NEEDINFO   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: jluke at cfl.rr.com               
@@ -44,6 +44,21 @@
 System.Globalization.NumberFormatInfo.ValidateParseStyleFloatingPoint
 (NumberStyles style)
    at Driver.Main(String[] args)
 
 .NET1.x bug?
 
+
+------- Additional Comments From sebastien at ximian.com  2005-12-12 15:09 -------
+Overall I think that Mono behaviour is better than MS.
+
+(a) .NET 2.0 final still throws the ArgumentException - but, IMHO,
+this isn't really nice to do from a TryParse method. 
+
+(b) As for the 1.1 profile the expected result value for "0dead" is
+57842 (MS 1.1 SP1) which doesn't match it's long value 57005 or a 64
+bits double (2.18e-319).
+
+For compatibility purpose I'll modify Mono to match 2.0 final (the
+ArgumentException). However, unless someone knows how to get the same
+result as MS, I will keep the current behaviour (false) for 1.x.
+