To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51838
                  Issue #:|51838
                  Summary:|uno2cpp: catch UNO non-exception-type exceptions
                          |properly
                Component:|udk
                  Version:|680m115
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P4
             Subcomponent:|code
              Assigned to:|sb
              Reported by:|sb





------- Additional comments from [EMAIL PROTECTED] Tue Jul 12 05:59:50 -0700 
2005 -------
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.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to