Probably it would be possible to do the same with OOo Basic, ie. add
that behaviour there as well (and it should be possible without
breaking existing code), e.g.
uur.XUnoUrlResolver.resolve(unoURL)
... as an option to
uur.resolve(unoURL)
...which could break existing code: Given the UNOIDL
interface x { void y(); };
interface y: x {};
interface z { y x(); };
the Basic expression
o.x.y;
could either be
o.x.y();
REM call x.y() on o
or
o.x().y();
REM first call z.x() on o, then call y.y() (aka x.y()) on the result
Interesting. Would have thought that in such cases the sequence (order)
of the listed interfaces is significant and determines which one is picked!
Then, how would you solve the following problem that you mentioned in
the other post in Java?
------------------ cut here -----------------
Just curious: how do you write down in ooRexx calls to method bar on
an object that implements the two interfaces
module m1 { interface XFoo { void bar(); }; };
module m2 { interface XFoo { void baz(); }; };
Hmm, good question.
Could you please hint how you would do that in Java (pseudo-code
suffices, ie. without casting)? Reason being, that whatever can be done
via Java can be done in ooRexx (using a very relaxed, almost pseudo-code
like syntax).
------------------ cut here -----------------
Regards,
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
