Difference between revisions of "Talk:Documentation/DevGuide/FirstSteps/Using Services"
| Line 2: | Line 2: | ||
For old style services, "multiple interface implementation" indeed would be more accurate. However, old style services (where a service implements multiple, unrelated interfaces) are deprecated, and should be superseded by new style services (where a service implements just one interface, but that interface is typically a multiple-inheritance interface that in turn inherits from multiple, otherwise unrelated interfaces). So, I am undecided whether or not [http://wiki.services.openoffice.org/w/index.php?title=Documentation%2FDevGuide%2FFirstSteps%2FUsing_Services&diff=94529&oldid=94472 Created "Multiple Interface Implementation" section out of what was on the page] is an improvement.--[[User:Sb|Sb]] 13:49, 7 October 2008 (CEST) | For old style services, "multiple interface implementation" indeed would be more accurate. However, old style services (where a service implements multiple, unrelated interfaces) are deprecated, and should be superseded by new style services (where a service implements just one interface, but that interface is typically a multiple-inheritance interface that in turn inherits from multiple, otherwise unrelated interfaces). So, I am undecided whether or not [http://wiki.services.openoffice.org/w/index.php?title=Documentation%2FDevGuide%2FFirstSteps%2FUsing_Services&diff=94529&oldid=94472 Created "Multiple Interface Implementation" section out of what was on the page] is an improvement.--[[User:Sb|Sb]] 13:49, 7 October 2008 (CEST) | ||
| + | |||
| + | Thanks, again, for commenting. I think I should go back with "multiple-inheritance interfaces" to be consistent with the rest of the guide. Perhaps a definition/discussion of that term should be added earlier in the guide, so that, whether or not we like the term, we all know what it means. The "Programmer's Guide" needs to make sense not only to C++ and Java folks, but also to Basic programmers, as well. (My background is Visual Basic, which, until VB.net, hasn't used interfaces.)--[[User:Cking|Cking]] 23:35, 7 October 2008 (CEST) | ||
Latest revision as of 21:35, 7 October 2008
I read that "multiple-inheritance interfaces" is more properly called "multiple interface implementation", so I made the change.--Cking 21:22, 5 October 2008 (CEST)
For old style services, "multiple interface implementation" indeed would be more accurate. However, old style services (where a service implements multiple, unrelated interfaces) are deprecated, and should be superseded by new style services (where a service implements just one interface, but that interface is typically a multiple-inheritance interface that in turn inherits from multiple, otherwise unrelated interfaces). So, I am undecided whether or not Created "Multiple Interface Implementation" section out of what was on the page is an improvement.--Sb 13:49, 7 October 2008 (CEST)
Thanks, again, for commenting. I think I should go back with "multiple-inheritance interfaces" to be consistent with the rest of the guide. Perhaps a definition/discussion of that term should be added earlier in the guide, so that, whether or not we like the term, we all know what it means. The "Programmer's Guide" needs to make sense not only to C++ and Java folks, but also to Basic programmers, as well. (My background is Visual Basic, which, until VB.net, hasn't used interfaces.)--Cking 23:35, 7 October 2008 (CEST)
