One way around the problem with future compatibilities in languages such as Basic would be the introduction of an (optional) import statement that would have the effect of moving a given interface to the front of the method search path for the module it's in.
import com.sun.star.text.XTextRange Sub Foo(text) MsgBox(text.getString()) End Sub would always mean the same, no matter if the object passed as text implements several interfaces with a getString() method, because XTextRange.getString() will always be found first. So if you properly decorate your modules with import statements for all the interfaces you use, you'll be save from any future interfaces messing up your code. Of course you still need syntax for explicitly specifying the interface a method comes from in order to use 2 methods of the same name from different interfaces in the same module. Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
