From c27e96fe92dab42cb1ca3ccf63164cb2c81ff7a6 Mon Sep 17 00:00:00 2001 From: Richard Brooksby Date: Sat, 8 Jun 2013 22:07:44 +0100 Subject: [PATCH] Adjusting statement that assertions aren't serious. Copied from Perforce Change: 182652 ServerID: perforce.ravenbrook.com --- mps/manual/source/release.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/mps/manual/source/release.rst b/mps/manual/source/release.rst index d780237bd7b..212b7cc92db 100644 --- a/mps/manual/source/release.rst +++ b/mps/manual/source/release.rst @@ -11,12 +11,12 @@ Release 1.112.0 Interface changes ................. -1. In the :term:`hot` (production) variety, the MPS now prints - assertion messages to standard error but does *not* terminate the - program. This is because most assertions do not indicate *fatal* - error conditions, and continuing gives the application a chance to - shut down safely and save work, or even to limp along indefinitely. - See :ref:`topic-error-assertion-handling`. +1. In the :term:`hot` (production) variety, the default assertion handler + now prints messages to standard error but does *not* terminate the + program. Even though assertions indicate serious problems in the + program, an end-user does not want an application to terminate when + there is a chance to shut down safely and save work, or even to limp + along indefinitely. See :ref:`topic-error-assertion-handling`. 2. The behaviour when an assertion is triggered is now configurable in the standard ANSI :term:`plinth` by installing an assertion