Re: Separation of concerns

That is a matter of generalization rather than separation of concerns.

Then what would be a good example for the usage of separation of
concerns?

However, the notion of -able (drawable, persistable, etc.) is often
symptomatic of an abuse of OO generalization that is related to
separation of concerns. This is a variation on the sort of composition
one finds in functional programming. One composes objects by providing
disparate responsibilities through inheritance (often multiple
inheritance). The resulting object is a hybrid of logically unrelated
groups of properties.

Agreed. I would rather put the draw method inside of the class A or B,
but I want to create this software to be a piece that shows good use
of the OO Priciples (for me that includes seperation of cencers).

Regards,
Thomas Kowalski

.