From fdf1fee658602b33c22c9b0e536b5d30dfb681b9 Mon Sep 17 00:00:00 2001 From: Emil Dotchevski Date: Tue, 22 Dec 2020 19:13:46 -0800 Subject: [PATCH] Added a link to LEAF in boost-exception.html --- doc/boost-exception.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/boost-exception.html b/doc/boost-exception.html index 45ecd94..046f8eb 100644 --- a/doc/boost-exception.html +++ b/doc/boost-exception.html @@ -19,7 +19,7 @@ -

NOTE: If you are using C++11 or newer and Boost 1.75 or newer, you might consider using Boost LEAF instead of Boost Exception.

+

NOTE: When targeting C++11 or newer and Boost 1.75 or newer is available, it is recommended to use Boost LEAF instead of Boost Exception. LEAF serves a similar purpose but it has a more elegant interface, it is more efficient, and works with or without exception handling -- yet understands Boost Exception error information for compatibility with legacy source code. This overview explains the differences between the two APIs (Boost Exception is not deprecated and will continue to be supported, including C++03 compatibility).

Introduction

The purpose of Boost Exception is to ease the design of exception class hierarchies and to help write exception handling and error reporting code.

It supports transporting of arbitrary data to the catch site, which is otherwise tricky due to the no-throw requirements (15.5.1) for exception types. Data can be added to any exception object, either directly in the throw-expression (15.1), or at a later time as the exception object propagates up the call stack.