[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: OO should break when broken(was re: the benefits of immutability)
- To: <address@hidden>
- Subject: RE: OO should break when broken(was re: the benefits of immutability)
- From: "Asokan Pichai" <address@hidden>
- Date: Tue, 2 Sep 2003 10:43:09 +0530
- Sender: address@hidden
- Thread-index: AcNw6f3ZqUjpBywDRyO7eH9UneEjCAAJp8JQ
- Thread-topic: OO should break when broken(was re: the benefits of immutability)
>> I trying to extend OpenMap classes, in and of themselves very useful,
>> and finding that I wished a few things had been put elsewhere rather
>> in than the classes I was extending.
>That is why I think Sather has it done right. You can only inherit from
>something abstract, i.e., sth that has no implementation at all. Reuse
>of implementation in Sather is separate from inheritance of interface.
IIRC, Scott Meyers recommends that in his (More) Effective C++ book.
"do not derive from a concrete class".