[Mono-bugs] [Bug 59638][Blo] Changed - MONO Beta 2 bug with XmlSerializer member ordering

[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 lluis@ximian.com.

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

--- shadow/59638	2004-06-09 10:07:06.000000000 -0400
+++ shadow/59638.tmp.15288	2004-06-10 06:41:30.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 59638
 Product: Mono: Class Libraries
 Version: unspecified
 OS: Red Hat 9.0
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: 001 One hour
 Priority: Blocker
 Component: Sys.XML
 AssignedTo: lluis@ximian.com                            
 ReportedBy: davidandrewtaylor@hotmail.com               
 QAContact: mono-bugs@ximian.com
@@ -134,6 +134,13 @@
 (_attributeMembers.Values)
 		list.Sort(new XmlTypeMapMemberComparer());
 		return list;
 	}
 }
  
+
+------- Additional Comments From lluis@ximian.com  2004-06-10 06:41 -------
+I commited your fix for GetReflectionMembers and another fix for the
+attribute issue. This last fix uses an extra array to keep the
+attributes in the correct order. I have not changed the Hashtable (my
+tets show that ListDictionary can be slower than a hashtable even with
+6 or 7 elements, and this may be a common case).