[Mono-bugs] [Bug 60227][Wis] Changed - System.Decimal class has different behaviour from MS implementation

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon May 8 11:05:53 EDT 2006

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.


--- shadow/60227	2006-05-08 10:35:17.000000000 -0400
+++ shadow/60227.tmp.2986	2006-05-08 11:05:53.000000000 -0400
@@ -60,6 +60,20 @@
 (double) and has been fixed.
 ------- Additional Comments From atsushi at ximian.com  2006-05-08 10:35 -------
 Umm, are there corresponding tests for this bug? I see two NotWorking
 tests in DoubleTest.cs but they seem very intended (notworking only
 under 1.x).
+------- Additional Comments From sebastien at ximian.com  2006-05-08 11:05 -------
+There aren't many test cases (bug 63902 may be one) because most of
+them were "fixed". The problem is that the fix isn't perfect(*) and is
+less than optimial (CPU wise).
+(*) The real problem is that our original decimal C code was made to
+be compatible with MS fx 1.0. Fx 1.1 changed the rules around
+decimals, so we (well I) fixed around that (not redesigned).
+So the bug is a remainder that the current situation isn't perfect and
+will, someday, need to be addressed. IMO it would be nice to reuse
+SqlDecimal code (C# port of the current C code) and remove the decimal
+from the runtime.

More information about the mono-bugs mailing list