Geeks With Blogs
Tim Watson blog
I am forever getting mixed up with this one. The proper way to do this depends on the semantics you want. If you want your Equals to test for object identity, you should override Object's implementation (which doesn't take into account inheritance properly). Object's "Equals" method is implemented like this... public class Object{ public virtual bool ......

I had an interesting question come up the other day: why override object's "Equals" method and/or the equality/inequality operators at all? Why not just compare objects in some dedicated function or other? After my initial shock died down (the question came from an OO developer), I realized there are several reasons. Let's consider these in the context ......

Assembly to source conversion: http://www.denisbauer.com/N... SQL 2005 Browser: http://www.denisbauer.com/N... Visual Studio Add-in: http://www.testdriven.net/r... ......

Martin Fowler has recently added some new Patterns of Enterprise Application Architecture to his site. Check them out here.



Copyright © Tim Watson | Powered by: GeeksWithBlogs.net