Difference between revisions of "Talk:Documentation/DevGuide/FirstSteps/Objects, Interfaces, and Services"
m |
|||
Line 5: | Line 5: | ||
At least in UNO (and also in Java, and, equating abstract classes with interfaces, also in C++), interfaces ''can'' inherit from (multiple) other interfaces. “Multiple inheritance” is an established term for this. Consequently, I undid most of your recent modifications.--[[User:Sb|Sb]] 15:43, 7 October 2008 (CEST) | At least in UNO (and also in Java, and, equating abstract classes with interfaces, also in C++), interfaces ''can'' inherit from (multiple) other interfaces. “Multiple inheritance” is an established term for this. Consequently, I undid most of your recent modifications.--[[User:Sb|Sb]] 15:43, 7 October 2008 (CEST) | ||
+ | |||
+ | Thanks for looking at it. I've had a hard time understanding interfaces. I'll post to the mailing list first, next time.--[[User:Cking|Cking]] 23:01, 7 October 2008 (CEST) |
Latest revision as of 21:01, 7 October 2008
I don't think the term "multiple-inheritance interfaces" makes sense. Objects can inherit, but how can an interface inherit anything? Perhaps a better term would be "nested interfaces": these could be defined as interfaces that, besides their own methods, include all the methods of other interfaces. Java doesn't support multiple-inheritance objects, so I doubt that OOo does. I'll put "nested interface" into the section on interfaces to see how it looks.
Also, I've called the single interface of a new-style service a composite interface. --Cking 20:17, 6 October 2008 (CEST)
At least in UNO (and also in Java, and, equating abstract classes with interfaces, also in C++), interfaces can inherit from (multiple) other interfaces. “Multiple inheritance” is an established term for this. Consequently, I undid most of your recent modifications.--Sb 15:43, 7 October 2008 (CEST)
Thanks for looking at it. I've had a hard time understanding interfaces. I'll post to the mailing list first, next time.--Cking 23:01, 7 October 2008 (CEST)