Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COHowever note that by altough correct and provable my answer is unlikely to be well accepted on a site like SO, which is entirely focus on implementation details and frequented by programmers who are for the most part totally unaware of the bigger picture. They've been learning OO, say, while learning Java and have been told in the process by countless totally wrong sources that Java only support single inheritance. Don't expect these kind of people to see the light and change their minds :)
      singulars
    2. COExtending interfaces in no way constitutes multiple inheritance. No implementation details are ever derived from an interface, it's merely a specification of what a class should contain (and implement). But if you're of a different opinion, feel free to elucidate.
      singulars
    3. CO@mikek: of course extending from several interface constitutes MI (on a funny sidenote, Java didn't get this wrong: you can write *interface A extends B,C*. And I specifically explained why in my answer "multiple interface inheritance" is "multiple inheritance". You're seriously confusing "code reuse" and "inheritance". Note that anything you think can't be done and hence ain't MI when extending from multiple Java interfaces can actually be done simply using delegation. Once again: show me **ANY** OOA/OOD using MI that cannot be trivially ported to Java using multiple interface inheritance...
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload