Closed libcg closed 6 years ago
I've learned to be wary of catch (...)
because it catches things you wouldn't think of as (C++) exceptions on some platforms. My experience was on Windows, where it catches "Windows Structured Exception Handling" exceptions (an old C thing built on LONGJMP), as well as debugger breakpoints.
Per the comment after the catch, the intent of the code here is that any exception which isn't a std::exception should just call terminate() when it hits the noexcept spec, which the language guarantees. That can probably be accomplished without the warning with another layer of indirection. I.e. put the code inside a function with no exception spec, then call it from the main function marked noexcept.
Hi, @libcg: I noticed you haven't signed the CLA yet, could you please sign it here: https://opensource.dropbox.com/cla/ Thanks a lot!
Now that https://github.com/dropbox/djinni/pull/378 is merged, I think that this PR may not be needed anymore, because I think booth PR address the same issue.
Replaced by #378
Fixes the following compilation error after updating to NDK r17: