E
Eric
Let's say I have a base class that implements IComparable<baseClass>. Really
it could be any interface but I'm picking that one for the sake of
discussion. In this class, equality and comparisons are based on a string
representation of it's attributes - a subclass may add an attribute but
still uses a string representation for equality and comparison.
So if I can avoid it, I'd like to have all my tests and code associated with
the base class. Must I have the subclass also implement
IComparable<subClass> and then make wrapper calls to the base class? Would I
be better off using composition than inheritance?
I may be working way too hard to save some work, but I'd like to explore the
idea.
Thanks,
Eric
it could be any interface but I'm picking that one for the sake of
discussion. In this class, equality and comparisons are based on a string
representation of it's attributes - a subclass may add an attribute but
still uses a string representation for equality and comparison.
So if I can avoid it, I'd like to have all my tests and code associated with
the base class. Must I have the subclass also implement
IComparable<subClass> and then make wrapper calls to the base class? Would I
be better off using composition than inheritance?
I may be working way too hard to save some work, but I'd like to explore the
idea.
Thanks,
Eric