/prog/ - Disallowing multiple inheritance is retarded

Name: Anonymous 2012-10-03 19:40

Because really, when the fuck are two functionally distinct supersets going to have a method of the same name? And if they do, why not just TELL IT TO USE THE CORRECT ONE?!

Plus I'm fucking retarded for not having already had this paradigm-altering insight.

Name: Anonymous 2012-10-03 19:48

go away Bjarne

Name: Anonymous 2012-10-03 20:14

Mathematically single inheritance multiple interface is more elegant since it collapses into just one possible unambiguous implementation.

Name: Anonymous 2012-10-03 21:17

Composition not inheritance.

Name: Anonymous 2012-10-03 23:53

2012
multiple ihneritance

http://en.wikipedia.org/wiki/Trait_(computer_programming)

Name: Anonymous 2012-10-03 23:55

2012
still using inheritance for polymorphism at all

Name: Anonymous 2012-10-04 0:05

Yup, traits/roles killed MI.

Name: Anonymous 2012-10-04 2:53

Sun got it right

Name: Anonymous 2012-10-04 4:25

I use multiple inheritance sometimes, e. g. when I have

class BaseReader

    def parse

...

class BaseWriter

    def store

...

class SomeFileShit(BaseReader, BaseWriter)

    def store # Different from the default

    # But parse is exactly the base case.

Sure, it is much more elegant in Haskell, but I ain't writin' no fuckin' Haskell on my day job muhfugga.

Name: Anonymous 2012-10-04 4:49

Sure, it's retarded, but is it Leah retarded?

Disallowing multiple inheritance is retarded

1 Name: Anonymous 2012-10-03 19:40

2 Name: Anonymous 2012-10-03 19:48

3 Name: Anonymous 2012-10-03 20:14

4 Name: Anonymous 2012-10-03 21:17

5 Name: Anonymous 2012-10-03 23:53

6 Name: Anonymous 2012-10-03 23:55

7 Name: Anonymous 2012-10-04 0:05

8 Name: Anonymous 2012-10-04 2:53

9 Name: Anonymous 2012-10-04 4:25

10 Name: Anonymous 2012-10-04 4:49