Re: [Pharo-users] Why single inheritance?

[Cameron Sanders via Pharo-users]

--- Begin Message ---

Laura,

Obviously, I should have let the experts answer, and I did not answer all
of your questions in that last quick-off-the-cuff
diss-the-strongly-typed-languages answer. My apologies.

For me, i like to keep the namespace clean. And one must admit, with
multiple inheritance, things can get confusing, and in some cases, the
wrong methods come into play. If one breaks free of inheritance as a means
to gain polymorphism, code re-usability can grow considerably, and the
ability to substitute classes to be used by a 3rd party libraries grows
with it.

I generally prefer delegation(/decoration) approaches to inheritance, in
part just to control the namespace and "interface" of a class.

Traits are still not widely available in different smalltalks, are they?

-Cam

On Wed, Jan 28, 2015 at 10:41 AM, Laura Risani <laura.ris...@gmail.com>
wrote:

> Hi all,
>
> What is the explanation why Smalltalk designers preferred single
> inheritance+traits to multiple inheritance? Why is the former better than
> the latter?
> Do traits let you share state also or only behavior?
>
> Best,
> Laura
>

--- End Message ---