Re: Separation of concerns

Thomas Kowalski schrieb:
Hi everyone,
I am currently quite confused about the separation of concerns things
and search here for enlightenment.
I have some classes. lets say A and B that shall implement a certain
interface (e.g. Drawable).
Now it would not be very nice if A and B would implement then directly
or?
Should I subclass like A_Draw and B_Draw or what is the current
pattern to solve this?

You can use AOP (aspect-oriented programming), mixins (abstract subclasses) or CoP (concept-oriented programming) or may be some other approach or technique (like inner methods). OOP is known to be inappropriate for this problem. In other words, in OOP it is not possible to effectively separate concerns (as this problem is currently interpreted).


Thanks a lot in advance,
Thomas Kowalski

--
http://conceptoriented.com
.

Relevant Pages

  • Re: Overloading abstract methods
    ... In his design the superclass is conceived ... There is a clear separation between the purpose of the ... superclass code and that of the subclass code, ... but that isn't how Rhino has chosen to factor ...
    (comp.lang.java.programmer)
  • Re: Separation of concerns
    ... CoP (concept-oriented programming) or may be some other approach or technique ... OOP is known to be inappropriate for this problem. ... I will allow that it is not an easy thing to design for separation of concerns, ...
    (comp.object)
  • Separation of concerns
    ... I am currently quite confused about the separation of concerns things ... and search here for enlightenment. ... pattern to solve this? ... Thomas Kowalski ...
    (comp.object)