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

[Magicloud Magiclouds]

On this subject, I think, any "content inherit" would lead to trouble
somehow. But is that the reason that we should totally cut them loose?
I mean the way of programming developing is easier making (writing),
easier maintaining. In fact, I think this is a fork in front of me:
Before any new thoughts/ideas of programming theroy came out, I have
to choose between much less code (and in this case, better organized
code/object structure. I mean the code level, not the bunch of
documents come along.) and easier maintenance.
Of course, I would be very glad if we could have better solution.

On Fri, Oct 30, 2009 at 3:46 PM, Martijn van Steenbergen
<martijn at van.steenbergen.nl> wrote:
> Magnus Therning wrote:
>>
>> IIRC James Gosling once said that if he were to design Java today he would
>> leave out classes.  I suppose partly due to many of the issues with "data
>> inheritance".
>
> This sounds interesting. Can you link us to an article, please?
>
> Thanks,
>
> Martijn.
>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>



-- 
竹密岂妨流水过
山高哪阻野云飞