Why doesn\'t C use nested exceptions to handle exceptions thrown from destructors?

Why doesn't C use nested exceptions to throw from destructors?

Understanding the Issue

Throwing exceptions from destructors introduces a dilemma: what to do when an exception is already in flight? Overwriting the existing exception or nesting the new exception within the existing one are potential solutions, but it was decided that terminating with std::terminate would be the standard approach.

Consideration of Nested Exceptions

C 11 introduced the std::nested_exception feature, which could potentially address the issue by nesting the old exception within the new one. However, this idea was not implemented.

Reasons for Non-Implementation

One reason for not using nested exceptions in this context is the fact that std::nested_exception has very limited usage, with only one known practical application: creating fully-annotated call stacks.

This example demonstrates how nesting exceptions provides a convenient way to add context and pinpoint errors during debugging:

<code class="cpp">#include <iostream>
#include <sstream>
#include <exception>

void rethrow(const std::string& context, ...) {
    std::ostringstream ss;
    ss <p>Expected Output:</p>
<pre class="brush:php;toolbar:false">exception: outer : abcd
exception:  inner : abcdabcd
exception:   really_inner
exception:    too long

The above example showcases the nesting of exceptions and demonstrates how this technique aids in tracing errors and understanding call stacks.

Despite the utility of nested exceptions in this specific scenario, the decision not to use them in the context of destructor exceptions was likely made due to the ease and reliability of terminating with std::terminate.

The above is the detailed content of Why doesn\'t C use nested exceptions to handle exceptions thrown from destructors?. For more information, please follow other related articles on the PHP Chinese website!