Timeline for answer to What is an interface in Java? by Imagist
Current License: CC BY-SA 3.0
Post Revisions
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2019 at 5:37 | review | Suggested edits | |||
| Apr 5, 2019 at 6:10 | |||||
| Apr 4, 2019 at 10:37 | review | Suggested edits | |||
| Apr 4, 2019 at 13:16 | |||||
| S Sep 19, 2017 at 7:50 | history | suggested | Anatoly Shamov | CC BY-SA 3.0 |
Documentation link removal. See https://meta.stackoverflow.com/questions/356294/removing-documentation-reputation-archive-and-links
|
| Sep 19, 2017 at 7:01 | review | Suggested edits | |||
| S Sep 19, 2017 at 7:50 | |||||
| May 23, 2017 at 12:17 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jan 2, 2017 at 14:01 | history | edited | RamenChef | CC BY-SA 3.0 |
added 8 characters in body
|
| S Aug 4, 2016 at 22:39 | history | suggested | NageN | CC BY-SA 3.0 |
Updated the documentation link
|
| Aug 4, 2016 at 20:00 | review | Suggested edits | |||
| S Aug 4, 2016 at 22:39 | |||||
| Sep 9, 2009 at 4:25 | vote | accept | Imagist | ||
| Aug 24, 2009 at 10:09 | comment | added | Gertjan | No, interfaces are not used for inheritance. Interfaces are just "contracts" that define the functions and members an class must have when implementing the interface. Interfaces cannot be used to work around the "extend issue" (which does not allow you to extend 2 or more classes). when extending a class the functionality of the class you extend is still accessible (through the extending class), but since an interface has no functionality you cannot use it to ommit the multiple inheritance restriction because members and functions need to be written in the implementing class. | |
| Aug 24, 2009 at 9:16 | comment | added | ante.sabo | interface is like a pipe through which you can access to different classes of objects in a standardized way. Since in Java you cannot extend more than one class, interface is here to satisfy need for more complex inheritance. | |
| Aug 24, 2009 at 8:50 | comment | added | Imagist | @Gertjan You are correct. However, I don't think the distinction between "inherits" and "implements" is all that important, especially considering that in many cases one both inherits and implements an abstract class. I chose to keep the naming scheme to be less confusing. | |
| Aug 24, 2009 at 8:45 | history | edited | Imagist | CC BY-SA 2.5 |
More prettyfying.
|
| Aug 24, 2009 at 8:40 | comment | added | Gertjan | One small remark, you call your class "InheritsFromTwoInterfaces", but when you use interfaces you are usually not speaking about Inheriting, but Implementing, this because the interface does not contain any logic and/or implementation you can inherit. Therefore it is better to speak about implementation (at least that is they learned me). | |
| Aug 24, 2009 at 8:35 | history | edited | Imagist | CC BY-SA 2.5 |
Prettying up.
|
| Aug 24, 2009 at 8:30 | history | answered | Imagist | CC BY-SA 2.5 |