Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index 

On 03/23/2012 04:59 PM, Tor Lillqvist wrote:

Hmm. OK, I think I get it, Java's RuntimeException (and the subclasses
of that) has significantly different semantics than that of its
Exception (and subclasses), unchecked vs. checked. The intent is that
the UNO exceptions be similarly divided when viewed on the Java side.
Presumably that can not be changed.


Yep.
So the confusion of using the same jfieldID across different classes only hurts for css.uno.Exception vs. css.uno.RuntimeException (which are not related by inheritance) and not elsewhere (where we potentially also reuse field or method IDs across classes related by inheritance -- did not look into the code whether that is actually the case)? In which case a fix in the JNI UNO bridge should not be too difficult (again, without actually looking at the code yet). 

Stephan

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.