diff --git a/doc/BOOST_ERROR_INFO.html b/doc/BOOST_ERROR_INFO.html index c3f2ef9..7abbb7f 100644 --- a/doc/BOOST_ERROR_INFO.html +++ b/doc/BOOST_ERROR_INFO.html @@ -16,6 +16,9 @@
#include <boost/exception/info.hpp>
namespace @@ -34,6 +37,9 @@ boost
The following example demonstrates how errno can be stored in exception objects using Boost Exception:
-#include <boost/exception.hpp> -#include <errno.h> -#include <iostream> - -typedef boost::error_info<struct tag_errno,int> errno_info; //(1) - -class my_error: public boost::exception, public std::exception { }; //(2) - -void -f() - { - throw my_error() << errno_info(errno); //(3) - } --
First, we instantiate the error_info template using a unique identifier -- tag_errno, and the type of the info it identifies -- int. This provides compile-time type safety for the various values stored in exception objects.
-Second, we define class my_error, which derives from boost::exception.
-Finally, (3) illustrates how the typedef from (1) can be used with operator<<() to store values in exception objects at the point of the throw.
-The stored errno value can be recovered at a later time like this:
-// ...continued
-
-void
-g()
- {
- try
- {
- f();
- }
- catch(
- my_error & x )
- {
- if( boost::shared_ptr<int const> err=boost::get_error_info<errno_info>(x) )
- std::cerr << "Error code: " << *err;
- }
- }
-The get_error_info() function template is instantiated with the typedef from (1), and is passed an exception object of any type that derives publicly from boost::exception. If the exception object contains the requested value, the returned shared_ptr will point to it; otherwise an empty shared_ptr is returned.
--
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
Sometimes the throw site does not have all the information that is needed at the catch site to make sense of what went wrong. Here is an example:
-#include <stdio.h> -#include <string> - -class -file_read_error - { - public: - - explicit - file_read_error( std::string const & fn ): - fn_(fn) - { - }; - - std::string const & - file_name() const - { - return fn_; - } - - private: - - std::string fn_; - }; - -void -file_read( FILE * f, void * buffer, size_t size ) - { - if( size!=fread(buffer,1,size,f) ) - throw file_read_error("????"); - }-
We have defined an exception class file_read_error which can store a file name, so that when we catch a file_read_error object, we know which file the failure is related to. However, the file_read function does not have the file name at the time of the throw; all it has is a FILE handle.
-One possible solution is to not use FILE handles directly. We could have our own class file which stores both a FILE handle and a file name, and pass that to file_read(). However, this could be problematic if we communicate with 3rd party code that does not use our class file (probably because they have their own similar class.)
-A better solution is to make class file_read_error derive (possibly indirectly) from boost::exception, and free the file_read() function from the burden of storing the file name in exceptions it throws:
-#include <boost/exception.hpp> -#include <stdio.h> -#include <errno.h> - -typedef boost::error_info<struct tag_errno,int> errno_info; - -class file_read_error: public boost::exception { }; - -void -file_read( FILE * f, void * buffer, size_t size ) - { - if( size!=fread(buffer,1,size,f) ) - throw file_read_error() << errno_info(errno); - }-
If file_read() detects a failure, it throws an exception which contains the information that is available at the time, namely the errno. Other relevant information, such as the file name, can be added in a context higher up the call stack, where it is known naturally:
-#include <boost/exception.hpp> -#include <boost/shared_ptr.hpp> -#include <stdio.h> -#include <string> - -typedef boost::error_info<struct tag_file_name,std::string> file_name_info; - -boost::shared_ptr<FILE> file_open( char const * file_name, char const * mode ); -void file_read( FILE * f, void * buffer, size_t size ); - -void -parse_file( char const * file_name ) - { - boost::shared_ptr<FILE> f = file_open(file_name,"rb"); - assert(f); - try - { - char buf[1024]; - file_read( f.get(), buf, sizeof(buf) ); - } - catch( - boost::exception & e ) - { - e << file_name_info(file_name); - throw; - } - }-
The above function is (almost) exception-neutral -- if an exception is emitted by any function call within the try block, parse_file() does not need to do any real work, but it intercepts any boost::exception object, stores the file name, and re-throws using a throw-expression with no operand (15.1.6). The rationale for catching any boost::exception object is that the file name is relevant to any failure that occurs in parse_file(), even if the failure is unrelated to file I/O.
-As usual, the stored data can be retrieved using get_error_info().
--
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
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 classes. 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.
@@ -333,7 +336,7 @@ my_exception: .... throw boost::enable_current_exception(my_exception()); -Unless enable_current_exception() is called at the time an exception object is used in a throw-expression, any attempt to copy it using current_exception() returns an exception_ptr which refers to an instance of unknown_exception.
+Unless enable_current_exception() is called at the time an exception object is used in a throw-expression, an attempt to copy it using current_exception() may return an exception_ptr which refers to an instance of unknown_exception. See current_exception() for details.
Instead of using the throw keyword directly, it is preferable to call boost::throw_exception(). This is guaranteed to throw an exception that derives from boost::exception and supports cloning.
diff --git a/doc/clone_exception.html b/doc/clone_exception.html deleted file mode 100644 index a594a56..0000000 --- a/doc/clone_exception.html +++ /dev/null @@ -1,55 +0,0 @@ - - -
- -#include <boost/exception/cloning.hpp>
-namespace
-boost
- {
- template <class T>
- exception_ptr clone_exception( T const & e );
- }
-T must be polymorphic.
-It is unspecified whether the return values of two successive calls to clone_exception() refer to the same exception object.
--
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
Boost Exception supports transporting of exception objects between threads through cloning. This system is similar to N2179, but because Boost Exception can not rely on language support, the use of enable_current_exception() at the time of the throw is required in order to use cloning.
When you catch a boost::exception, you can call current_exception() to get an exception_ptr object:
-#include <boost/exception_ptr.hpp> -#include <boost/thread.hpp> -#include <boost/bind.hpp> - -void do_work(); //throws cloning-enabled boost::exceptions - -void -worker_thread( boost::exception_ptr & error ) - { - try - { - do_work(); - error = boost::exception_ptr(); - } - catch( - ... ) - { - error = boost::current_exception(); - } - }-
In the above example, note that current_exception() captures the original type of the exception object. The exception can be thrown again using the rethrow_exception() function:
-// ...continued - -void -work() - { - boost::exception_ptr error; - boost::thread t( boost::bind(worker_thread,boost::ref(error)) ); - t.join(); - if( error ) - boost::rethrow_exception(error); - }-
current_exception() could fail to copy the original exception object in the following cases:
-Regardless, the use of current_exception() and rethrow_exception() in the above examples is well-formed.
--
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
#include <boost/exception_ptr.hpp>
namespace @@ -30,6 +33,9 @@ boost + + +
diff --git a/doc/current_exception.html b/doc/current_exception.html index 531aff5..765f813 100644 --- a/doc/current_exception.html +++ b/doc/current_exception.html @@ -16,6 +16,9 @@Boost Exception
#include <boost/exception_ptr.hpp>
namespace @@ -40,6 +43,9 @@ boost exception_ptr
unknown_exception
#include <boost/exception/enable_current_exception.hpp>
namespace
@@ -38,7 +41,7 @@ my_exception:
....
throw boost::enable_current_exception(my_exception());
-Unless enable_current_exception() is called at the time an exception object is used in a throw-expression, any attempt to copy it using current_exception() returns an exception_ptr which refers to an instance of unknown_exception.
+Unless enable_current_exception() is called at the time an exception object is used in a throw-expression, an attempt to copy it using current_exception() may return an exception_ptr which refers to an instance of unknown_exception. See current_exception() for details.
Instead of using the throw keyword directly, it is preferable to call boost::throw_exception(). This is guaranteed to throw an exception that derives from boost::exception and supports cloning.
#include <boost/exception/enable_error_info.hpp>
namespace @@ -35,6 +38,9 @@ boost Tutorial: Integrating Boost Exception in Existing Exception Class Hierarchies
throw_exception
#include <boost/exception/enable_exception_cloning.hpp>
-namespace
-boost
- {
- template <class T>
- ---unspecified--- enable_exception_cloning( T const & e );
- }
-T must have an accessible no-throw copy constructor
-An object of unspecified type which derives publicly from T. That is, the returned object can be intercepted by a catch(T &).
-This function is designed to be used directly in a throw-expression to enable the cloning support in Boost Exception. For example:
-class
-my_exception:
- public std::exception
- {
- };
-
-....
-throw boost::enable_exception_cloning(my_exception());
-Unless enable_exception_cloning() is called at the time an exception object is used in a throw-expression, any attempt to copy it using clone_exception() returns an exception_ptr which refers to an instance of unknown_exception.
-Instead of using the throw keyword directly, it is preferable to call boost::throw_exception(). This is guaranteed to throw an exception that derives from boost::exception and supports cloning.
--
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
#include <boost/exception/info.hpp>
namespace
@@ -56,6 +59,9 @@ typedef boost::error_info
Tutorial: Integrating Boost Exception in Existing Exception Class Hierarchies
Tutorial: Logging of boost::exception Objects
#include <boost/exception/exception.hpp>
namespace @@ -79,6 +82,9 @@ boost Tutorial: Transporting of Arbitrary Data to the Catch Site
Tutorial: Transporting of Exceptions between Threads
This header file contains the following definitions/declarations:
+ + +
This header file contains the following definitions/declarations:
+ + +
This header file contains the following definitions/declarations:
+ + +
This header file contains the following definitions/declarations:
+ + +
This header file contains the following definitions/declarations:
+ + +
This header file contains the following declaration:
namespace
@@ -24,6 +27,9 @@ boost
template <class Tag, class T>
class error_info;
}
+
+
+
This header file contains the following definitions/declarations:
+ + +
This header file includes all other header files of Boost Exception:
+ + +
#include <boost/exception_ptr.hpp>
namespace @@ -35,6 +38,9 @@ boost enable_current_exception
rethrow_exception
virtual char const * what() const throw();
#include <boost/exception/info.hpp>
namespace @@ -35,6 +38,9 @@ boost error_info
exception
The code snippet below demonstrates how boost::tuple can be used to bundle the name of the function that failed, together with the reported errno so that they can be added to exception objects more conveniently together:
-#include <boost/exception/info_tuple.hpp> -#include <boost/shared_ptr.hpp> -#include <stdio.h> -#include <string> -#include <errno.h> - -typedef boost::error_info<struct tag_file_name,std::string> file_name_info; -typedef boost::error_info<struct tag_function,char const *> function_info; -typedef boost::error_info<struct tag_errno,int> errno_info; -typedef boost::tuple<function_info,errno_info> clib_failure; - -class file_open_error: public boost::exception { }; - -boost::shared_ptr<FILE> -file_open( char const * name, char const * mode ) - { - if( FILE * f=fopen(name,mode) ) - return boost::shared_ptr<FILE>(f,fclose); - else - throw file_open_error() << - file_name_info(name) << - clib_failure("fopen",errno); - }-
Note that the members of a boost::tuple are stored separately in exception objects; they can only be retrieved individually, using get_error_info().
--
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
Class boost::exception provides a virtual member function what(), with a signature identical to the familiar std::exception::what() function. The default implementation returns a string value that is not presentable as a friendly user message, but because it is generated automatically, it is useful for debugging or logging purposes. Here is an example:
#include <boost/exception.hpp>
@@ -43,6 +46,9 @@ g()
#include <boost/exception/info.hpp>
#include <boost/exception/info_tuple.hpp>
namespace @@ -50,6 +53,9 @@ boost Tutorial: Integrating Boost Exception in Existing Exception Class Hierarchies
Tutorial: Logging of boost::exception Objects
#include <boost/exception_ptr.hpp>
namespace @@ -30,6 +33,9 @@ boost
#include <boost/throw_exception.hpp>
namespace @@ -37,6 +40,9 @@ boost enable_current_exception
Tutorial: Transporting of Exceptions between Threads
This header file contains the following definitions/declarations:
+ + +
All exception types that derive from boost::exception can be used as type-safe containers of arbitrary data objects, while complying with the no-throw requirements (15.5.1) of the ANSI C++ standard for exception classes. Data can be added to a boost::exception at the time of the throw, or at a later time.
#include <boost/exception_ptr.hpp>
namespace @@ -35,6 +38,9 @@ boost current_exception
enable_current_exception
Here is how cloning can be enabled in a throw-expression (15.1):
-#include <boost/exception/enable_current_exception.hpp> -#include <boost/exception/info.hpp> -#include <stdio.h> -#include <errno.h> - -typedef boost::error_info<struct tag_errno,int> errno_info; - -class file_read_error: public boost::exception { }; - -void -file_read( FILE * f, void * buffer, size_t size ) - { - if( size!=fread(buffer,1,size,f) ) - throw boost::enable_current_exception(file_read_error()) << - errno_info(errno); - }-
-
-
-
-Copyright (c) 2006-2008 by Emil Dotchevski and Reverge Studios, Inc.
-Distributed under the Boost Software License, Version 1.0.
-
Some exception hierarchies can not be modified to make boost::exception a base type. For this case, the enable_error_info() function template can be used to make exception objects derive from boost::exception anyway. Here is an example:
#include <boost/exception.hpp>
@@ -49,6 +52,9 @@ my_container