From a9ec93e70c09ca6fb4f1df40750952074e84d1f1 Mon Sep 17 00:00:00 2001
From: wolf <wolf@0785d39b-7218-0410-832d-ea1e28bc413d>
Date: Thu, 10 Jan 2002 10:22:35 +0000
Subject: [PATCH] new exception stuff

git-svn-id: https://svn.dealii.org/trunk@5373 0785d39b-7218-0410-832d-ea1e28bc413d
---
 deal.II/doc/news/2001/c-3-2.html | 21 ++++++++++++++++++---
 1 file changed, 18 insertions(+), 3 deletions(-)

diff --git a/deal.II/doc/news/2001/c-3-2.html b/deal.II/doc/news/2001/c-3-2.html
index 49fecc549c..b585ed0fb4 100644
--- a/deal.II/doc/news/2001/c-3-2.html
+++ b/deal.II/doc/news/2001/c-3-2.html
@@ -107,13 +107,28 @@ documentation, etc</a>.
 <h3>base</h3>
 
 <ol>
+  <li> <p>
+       New: the <code
+       class="member">deal_II_exceptions::set_additional_assert_output</code>
+       function allows to set additional output to be printed upon
+       triggering an <code class="member">Assert()</code> call. This
+       is helpful for parallel applications where you only see the
+       text of the message but do not know from which cluster node it
+       stems.
+       <br>
+       (WB 2002/01/10)
+       </p>
+
   <li> <p>
        Changed: when an assertion fails in the <code
        class="member">Assert()</code> function, the program is usually
        aborted. Don't abort it any more if there is an active C++
-       somewhere since we would lose its message if we aborted the
-       program. In that case only report the error and write out an
-       indication why we do not abort the program any more.
+       exception somewhere since we would lose its message if we
+       aborted the program. In that case only report the error and
+       write out an indication why we do not abort the program any
+       more. On the other hand, also suppress output of further failed
+       <code class="member">Assert()</code> calls, since they often
+       are follow-ups of the first one.
        <br>
        (WB 2002/01/09)
        </p>
-- 
2.39.5