Re: [Haskell-cafe] How to fulfill the "code-reuse" destiny of OOP?

Magicloud wrote:

I am not saying that the code has to be in OO style. When I say OO is general, I mean I am thinking in OO style. This reflects on modeling, program structure, even code organization. Style is how we present things. I think that is less important than how we think about things.

Style is irrelevant to the larger theorems of the universe which tells us that OOP must be granular in architecture (composability will force it, else code has to be re-written), thus I cross link this thread to "Base classes can be _ELIMINATED_ with interfaces": http://www.haskell.org/pipermail/haskell-cafe/2009-November/068432.html