[Mono-bugs] [Bug 59425][Nor] Changed - Decimal formatting bug in MONO Beta 3

[bugzilla-daemon@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 davidandrewtaylor@hotmail.com.

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

--- shadow/59425	2004-06-05 13:34:42.000000000 -0400
+++ shadow/59425.tmp.20812	2004-06-15 01:16:56.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 59425
 Product: Mono: Class Libraries
 Version: unspecified
 OS: Red Hat 9.0
 OS Details: 
-Status: RESOLVED   
-Resolution: DUPLICATE
+Status: REOPENED   
+Resolution: 
 Severity: 001 One hour
 Priority: Normal
 Component: System
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: davidandrewtaylor@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Decimal.ToString() minor formatting bug in MONO Beta  1&2
+Summary: Decimal formatting bug in MONO Beta 3
 
 Description of Problem:
 I found a slight inconsistency (that I will call a bug) when using MONO 
 when calling .ToString() on a Decimal type.  While both MS.NET and MONO 
 output 0 as "0", and 5.37 as "5.37" the inconsistency is for exact 
 numbers (integers).  So for all exact numbers other than 0, such as 1 or 
@@ -67,6 +67,28 @@
 Additional Information:
 
 ------- Additional Comments From atsushi@ximian.com  2004-06-05 13:34 -------
 
 
 *** This bug has been marked as a duplicate of 56740 ***
+
+------- Additional Comments From davidandrewtaylor@hotmail.com  2004-06-15 01:16 -------
+I am reopening this bug report.  It was originally closed as a 
+duplicate of 56740, which stated that the bug is a compiler problem 
+and that when compiled with MCS and then run on MS.NET the same 
+output occurs.  This is very different than the bug I am reporting 
+here.
+
+Note that if you do this:
+string num = "5.00";
+Double n = Double.Parse(num);
+Console.WriteLine("Output is : " + n);
+
+MS.NET will output "5.00"
+MONO will output "5"
+
+Also note that if I compile with MCS and then run the generated 
+assembly on MS.NET I get the correct "5.00" output.  So this is 
+definately NOT a MCS compiler bug it is a library bug.
+
+It would be good to get this fixed before we ship v1.0
+