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.)