I would like to once again thank Tobias Schwinger, the review manager for Boost Exception, and to everyone who participated in the review process. Current documentation and source code can be downloaded from: http://www.revergestudios.com/boost-exception/boost-exception.html I have updated Boost Exception with the following requests and suggestions from the review: - added support for exception cloning - simplified the syntax for adding data to exceptions - added support for combining data into boost::tuple instead of the requested support for grouping of error_info objects - modified boost::throw_exception to ensure that all exceptions emitted from it support cloning and adding of arbitrary data types. The last change introduces dependency of throw_exception.hpp on a couple of boost components: intrusive_ptr and detail/atomic_count. Also, I know that my changes to boost::throw_exception are not compatible with older compilers such as VC6, or BCC5, or GCC295, etc. It might be possible to work around this, but I'm wondering if it's worth the effort. I think that it is reasonable to simply disable Boost Exception for these compilers (or else my throw_exception.hpp change would break things like shared_ptr which do work with these old compilers.) Let's discuss this issue before I submit the Boost Exception source code to SVN. Emil Dotchevski http://www.revergestudios.com/reblog/index.php?n=ReCode