Arthur has used the word "unjavaish", but you should keep in mind that
you use a component technology and that you can use the same API from
different languages. That should not mean that it would be impossible to
make Java UNO more Java like (today). See for example the newer .NET
UNO language binding which is smoother to use in a .NET env than Java
UNO in Java because we have learned.
But currently the compatibility is still more important and we don't
want to break existing solutions.
Absolutely. Breaking existing applications using UNO would be bad. I've
more been looking at how I should organize my own work which in the end
will need some sort of additional layer anyway.
You can be sure that we have this on our radar ...
Overall, it would be interesting to know how an incompatible change of
the API and maybe UNO would be accepted.
I wonder whether it would make sense to offer additional newly designed
interfaces in addition to the existing so people could program more
"javaish" or "pythonique" or whatever while maintaining backwards
compatibility.
Greetings
Arthur
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
