王在祥 wrote:
The Java UNO language binding predates Java 5 by some years. That might
explain why some of its features look strange or less than optimal in a
Java 5 context. Also, we try hard to keep the Java UNO language binding
and Java UNO environment compatible with Java 1.3.
Sure. Is it possible to support both Java 1.3 and Java 5(with new features)?
I would like to stick with a single Java language binding for the time
being, so things should not be incompatible between 1.3 and 5 (e.g., it
is not viable to use T[] for 1.3 out parameters and OutHolder<T> for 5
out parameters). One place where using 5 features worked well was in
adding polymorphic struct types to UNO, which are mapped to generic
classes in Java 5 and their type-erased counterparts in Java 1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
