|
|
On 8/14/2012 4:15, Warp wrote:
> clipka<ano### [at] anonymousorg> wrote:
>> As current widespread belief is that virtually all multiple inheritance
>> use cases can be covered with the interface approach, it seems to make
>> sense to avoid this extra overhead.
>
> Only if you don't mind the need for code repetition with interfaces.
I might have asked this before, but do you have any good (hopefully generic)
examples of where MI really helps out?
--
Darren New, San Diego CA, USA (PST)
"Oh no! We're out of code juice!"
"Don't panic. There's beans and filters
in the cabinet."
Post a reply to this message
|
|