Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[except.terminate] Better describe the function terminate #7281

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[except.terminate] Better describe the function terminate #7281

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions source/exceptions.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1012,9 +1012,10 @@

\pnum
\indextext{\idxcode{terminate}}%
% FIXME: What does it mean to abandon exception handling?
In some situations, exception handling is abandoned
for less subtle error handling techniques.
Some errors in a program cannot be recovered from, such as when an exception
is not handled or a \tcode{std::thread} object is destroyed while its thread
function is still executing. In such cases,
the function \tcode{std::terminate}\iref{exception.terminate} is invoked.
\begin{note}
These situations are:
\indextext{\idxcode{terminate}!called}%
Expand Down Expand Up @@ -1108,8 +1109,6 @@

\pnum
\indextext{\idxcode{terminate}}%
In such cases,
the function \tcode{std::terminate} is invoked\iref{exception.terminate}.
In the situation where no matching handler is found, it is
\impldef{stack unwinding before invocation of \tcode{std::terminate}}
whether or not the stack is unwound
Expand Down
Loading