[Mono-bugs] [Bug 78799][Wis] Changed - Missing operator == on Uri class

[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 alan.mcgovern at gmail.com.

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

--- shadow/78799	2006-08-01 08:10:26.000000000 -0400
+++ shadow/78799.tmp.9932	2006-08-01 10:46:04.000000000 -0400
@@ -82,6 +82,22 @@
 
 BTW Uri is one of the best class everyone who had ever fixed bugs
 doesn't want to touch again because this class is extremely annoying
 and people always try to push it away to anyone else (obvisouly ximian
 guys are too busy to keep care on this trivial fruitless class). If
 someone takes care of this class, it would be awesome.
+
+------- Additional Comments From alan.mcgovern at gmail.com  2006-08-01 10:46 -------
+Just to point out the obvious, but that version of operator== will
+return false if both u1 and u2 are null, leading to much confusion.
+        -------------------------------
+But thats the behaviour it should have (i think)! I thought they can
+only be equal if both u1 and u2 are not null. Have i misunderstood
+what was meant in MSDN?
+
+http://msdn2.microsoft.com/en-us/library/system.uri.op_inequality.aspx
+
+"If either parameter is a null reference (Nothing in Visual Basic),
+this method returns true."  <--- "This Method" means op_inequality
+
+But in MS.NET, if you compare two null System.URI's it returns true,
+so it must be right...