Issue 51838 - uno2cpp: catch UNO non-exception-type exceptions properly
Summary: uno2cpp: catch UNO non-exception-type exceptions properly
Status: ACCEPTED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: 680m115
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-12 13:59 UTC by Stephan Bergmann
Modified: 2017-05-20 11:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2005-07-12 13:59:50 UTC 
In all the different bridges/source/cpp_uno bridges, when calling from binary
UNO to C++, all exceptions are caught via "catch (...)" and translated into an
any.  C++ exceptions for which there is no corresponding UNO type are mapped to
com.sun.star.uno.RuntimeExceptions.  However, C++ exceptions that represent
non-exception UNO types (e.g., "throw com::sun::star::uno::Uik()") are not
mapped to com.sun.star.uno.RuntimeException.  Theoretically, all this would not
be an issue, as the C++ mapping of a UNO interface method should have an
exception specification that only allows UNO exceptions, but for example on
unxlngi6 we compile with -fno-enforce-eh-specs.
Comment 1 Stephan Bergmann 2005-07-12 14:00:41 UTC 
accepted
Comment 2 Marcus 2017-05-20 11:31:27 UTC 
Reset assigne to the default "issues@openoffice.apache.org".