diff options
author | Stephan Bergmann <sbergman@redhat.com> | 2015-06-30 17:07:59 +0200 |
---|---|---|
committer | Stephan Bergmann <sbergman@redhat.com> | 2015-06-30 17:07:59 +0200 |
commit | 14255b68e0b3a5155a588a16096c523156b1ff55 (patch) | |
tree | 43aa7438b774acf8f9299bf819a0b2b233262c09 /bridges | |
parent | 26d1a597a4c2258b652434856198c0ee8e1af87f (diff) |
Coverity 1308555, 1308562, 1308600: Drop some SAL_THROW_EXTERN_C
...from most rtl/bootstrap.h functions. They are effectively only called from
C++ code (there is no plain C UNO binding), so it should be fine to let std
exceptions (like bad_alloc or length_error) propagate from their implementations
to call sites.
(The exception is rtl_bootstrap_args_close, which is typically called from C++
dtors, so should not throw anyway.)
This would strictly speaking be an [API CHANGE], but it should make no practical
difference whether a process terminates abruptly because an exception cannot
pass through a SAL_THROW_EXTERN_C() nothrow specification or because legacy
client code does not expect exceptions to be thrown from functions from which
SAL_THROW_EXTERN_C() has now been removed.
Change-Id: I08e8479e9c5731e46021aadd6a725c1793024d10
Diffstat (limited to 'bridges')
0 files changed, 0 insertions, 0 deletions