[Mono-bugs] [Bug 75196][Nor] New - interop problem with serialization and deserialization of float and double

[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 roeie at mainsoft.com.

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

--- shadow/75196	2005-06-09 10:59:50.000000000 -0400
+++ shadow/75196.tmp.14793	2005-06-09 10:59:51.000000000 -0400
@@ -0,0 +1,42 @@
+Bug#: 75196
+Product: Mono: Class Libraries
+Version: 1.0
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: roeie at mainsoft.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: interop problem with serialization and deserialization of float and double
+
+Description of Problem:
+when trying to serialize the objects "double.MaxValue" 
+and "float.MaxValue" the serialization writes it in precision of 15 in 
+case of double and precision 7 in case of float, which is the default, 
+while the .NET framework writes these values in precision of 17 and 9.
+This cause the deserialization loose information and the deserialized 
+object to be different than the serialized one.
+
+Steps to reproduce the problem:
+1. serialize double.MaxValue to a file
+2. deserialize the object.
+3. compare the serialized object to the deserialized one using equals
+4. repeat stages 1-3 for float.MaxValue
+   
+Actual Results:
+   comparing these objects using equals results in false
+
+Expected Results:
+   the values should be equals
+
+How often does this happen? 
+   every time.
+
+Additional Information: