I have no idea how pyuno does it. But note that this problem was
there from the beginning, and has nothing to do with the addition of
multiple-inheritance interfaces. There are, for example, already
cases where one UNO object implements both XComponent and
XEventBroadcaster, and I have no idea how pyuno handles a call to
addEventListener on such an object. However, since this problem is
there from the beginning, I assume that the designers of pyuno took
care of that in an appropriate manner.
On second thought, all "dynamic" UNO language bindings (where
statically you can call any method of any UNO interface that a given
UNO object supports on that object, without mentioning the specific
interface, and where dynamically the runtime dispatches the method
call to the correct interface) are broken: A method call (with
whatever actual syntax)
someUnoObj#foo()
will work as long as the UNO object referenced by someUnoObj only
implements one interface that defines method foo, but will fail as
soon as that object also implements another such interface.
:(
Well, but that would induce that one should always explicitly request the interface (this could be
done in a somewhat "nicer" form than in C++/Java for Basic and the like). Then this
problem should not really pop-up (plus it makes it clearer to the coder which logical
"part" of the object s/he is addressing).
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
