> Unless I have a completely wrong idea about inheritance of course, but afaik a key element of inheritance was to 'take what you need' and 'leave out what you can'
A better idea is to say "put everything in it's proper place, and only write the code once". So in your example, putting everything in one base class is fine. If you were writing a framework of some kind, and wanted to limit what other programmers could do with each class - then you would need to seperate things out.
A better idea is to say "put everything in it's proper place, and only write the code once". So in your example, putting everything in one base class is fine. If you were writing a framework of some kind, and wanted to limit what other programmers could do with each class - then you would need to seperate things out.