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

On 03/21/2012 11:37 AM, Michael Stahl wrote:

for the case where it is a good idea to check exceptions (e.g. Java UNO
bridge, which cannot throw exceptions to the Java side that are not
declared on the interface), a runtime catch-all check should be
sufficient also.
Yep, guards to catch attempts of throwing anything not allowed by UNO across a bridge are generally in place. 


but i wonder if there is any compatibility concern here; i'd be more
comfortable if we only removed the exceptions specifications for LO4 and
not earlier.
Removing exception specifications from the C++ headers generated by cppumaker and from C++ classes defined in the URE interface should actually be compatible. 

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.