Well, as ooRexx uses Java (instead of C++) for the bridging, the solution would be the same as for Java. Or could object "o" have two different interfaces by the same name? If so, then it would be possible to explicitly query the interface supplying the class object for the respective interface, like you show in your example (except, I would then explicitly use m1.XFoo.class and m2.XFoo.class in queryInterface() instead)..The point I tried to make is that inOh, o.k., then this is how you would do it in ooRexx:... cut ...In Java: Originally, I had thought of something like: o~m1~XFoo~baror maybe: o~m1.XFoo~bar[this way being able to unambiguously resolve the interface by choosing resp. qualifying its name with the module-name making it distinguishable from m2.XFoo] but became unsure, hence my request for a Java example. In that Java example I assumed (probably falsely) that object "o" possesses the XFoo interface from m1 (but not from m2) by the name "XFoo", which then can be easily addressed by ooRexx (as there would not be a reason to distinguis between the two). If both interfaces could be present in "o", then you need to qualify it with so many names as to make it unambiguously clear, which XFoo one wants to use (one possibility in ooRexx could then be "o~m1.XFoo~bar", although it is not implemented that way in the present beta, but could be added, if that problem really can pop-up). ---rony P.S.: It still looks a little bit strange to me that the module name m1 resp. m2 would not be used for uniquely identifying which XFoo you would like to address. |
- Re: [api-dev] multiple-inheritance interafces and method... Rony G. Flatscher
- Re: [api-dev] multiple-inheritance interafces and m... Rony G. Flatscher
- Re: [api-dev] multiple-inheritance interafces and m... Stephan Bergmann
- Re: [api-dev] multiple-inheritance interafces a... Rony G. Flatscher
- Re: [api-dev] multiple-inheritance interafces and m... Stephan Bergmann