Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


From [Using UNO from
Automation](https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Bridge/Using_UNO_from_Automation):

    Different interfaces can have functions with the same name. There is no
way to call a function which belongs to a
    particular interface, because interfaces can not be requested in
Automation. If a UNO object provides two functions
    with the same name, it is undefined which function will be called. A
solution for this issue is planned for the future.

This page was last modified on 13 May 2009. Has there been any resolution to
the issue since then?

Also, even if the two functions have the same name, overloads could be
resolved based on the number and/or types of arguments passed in. Is this
actually done?

(I am trying to generate Typescript definitions for the UNO API
(https://github.com/zspitz/ts-activex-gen) and I have 14 instances where a
type implements two interfaces with conflicting member names.)



--
Sent from: http://nabble.documentfoundation.org/Users-f1639498.html

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.