Hi Stephan > One case where this problem occurs in practice is with > com.sun.star.lang.XComponent and > com.sun.star.document.XEventBroadcaster. I just learned that Andreas > Schlüns is probably going to add a new > com.sun.star.document.XDocumentEventBroadcaster (or similar) that will > have the same functionality as XEventBroadcaster, but using method names > that do not clash with XComponent. Thus, in this specific case the > solution can be to inherit from XDocumentEventBroadcaster instead of > XEventBroadcaster (which you might still want to offer via the > query-interface mechanism on your objects, for backwards compatibility), > instead of using the general solution outlined above. >
I am slightly disturbed by this, 2 interfaces with the same function names. Has any consideration being given to language-bindings that do not use the query-interface mechanism ? I.e pyuno where all interfaces for a service are returned ? How would pyuno or language_bindings that do not use the query-interface mechanism resolve which method to use? Regards, -- Darragh Sherwin PWB Implementations Manager http://www.propylon.com/solutions/parliament/index.html +353-1-4927456 +353-87-1204654 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
