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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79714 --- shadow/79714 2007-02-26 06:36:18.000000000 -0500 +++ shadow/79714.tmp.3856 2007-02-26 06:43:04.000000000 -0500 @@ -10,13 +10,12 @@ Component: System AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: -Cc: Summary: SortedList "Contains" sometimes fails with "string" keys Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: @@ -61,6 +60,25 @@ ------- Additional Comments From [EMAIL PROTECTED] 2007-02-26 06:36 ------- Created an attachment (id=18782) Simplified test case + +------- Additional Comments From [EMAIL PROTECTED] 2007-02-26 06:43 ------- + +I was able to whittle the test case down to a 3-way string comparison +that gives inconsistent results (see above attachment 18782). + +Of course, fixing that may not fix the whole issue, but it would be a +start. + +Some notes: +- The original test case (attachment 17887) works fine for me if the +SortedList is constructed with +CaseInsensitiveComparer.DefaultInvariant as the IComparer, but the +problems are there if Comparer.DefaultInvariant is used - I guess case +sensitive comparison is the underlying problem. +- This bug may be related to <a +href="http://bugzilla.ximian.com/show_bug.cgi?id=78748";>Bug 78748</a>, +which also was a collection problem caused by broken string comparisons. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
