On Tue, Jun 19, 2012 at 10:11 AM, Robert Ramey <ramey@rrsd.com> wrote:
b) boost::throw_exception should be rolled back to it's orginal meaning.
Reason:The problem here is that using something from the main boost namespace creates and unexpected and hidden dependency on another library. This occcurs without the library user getting notified at all. Much care has been expended so that those things directly inside the boost namespace (excluding convenience headers) be things which DO NOT create dependencies on other libraries. The current definition of boost::throw_exception is the only exception to this.
It isn't an exception, there are many other libraries that use the main boost namespace. FYI boost::throw_exception is a documented part of Boost Exception: www.boost.org/doc/libs/release/libs/exception/doc/throw_exception.html. In terms of dependencies, boost/throw_exception.hpp is extremely light, orders of magnitude lighter than boost/config.hpp, which is the low water mark for Boost dependencies. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode