>>>>In fact you never use a base class if you can help it. You inherit not cut and paste if you want to change/modify functionality.
>>>
>>>This seems contradictory. Can you explain?
>>
>>I don't think Bernard meant you should never use base classes. I think he meant if you want to change the functionality you should inherit rather than cut and paste. (Well, duh).
>
>He says don't use a base class, but to inherit. What will you inherit from? Unless I am missing something that doesn't make sense at all.

Maybe he had Visual FoxPro in mind. It has a very small number of base classes, most of them GUI controls. In that case it would probably make sense to inherit from each of them and work at that level. In .NET, where there are hundreds if not thousands of base classes, obviously that would be asinine.

That's just speculation. I should let Bernard clarify for himself.