Boost logo

Boost :

Subject: Re: [boost] [Stacktrace] review
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2016-12-15 01:53:34

On Wed, Dec 14, 2016 at 10:03 PM, Robert Ramey <ramey_at_[hidden]> wrote:

> On 12/14/16 5:47 PM, Peter Dimov wrote:
>> Robert Ramey wrote:
>> This made many libraries dependent on the new library boost.exception
>>> which had multiple repercussions - one of which is that
>>> boost.exception has now become a "core library" - not sure what that
>>> is supposed to mean.
>> No, throw_exception is its own mini-library now. It depends on nothing
>> but Assert and Config.
>> C:\Projects\boost-git\boost>dist\bin\boostdep.exe throw_exception
>> Primary dependencies for throw_exception:
>> assert:
>> <boost/current_function.hpp>
>> from <boost/throw_exception.hpp>
>> config:
>> <boost/config.hpp>
>> from <boost/throw_exception.hpp>
>> <boost/detail/workaround.hpp>
>> from <boost/throw_exception.hpp>
> I meant that every library which used BOOST_THROW_EXCEPTION now depends
> upon boost/throw_exception. Am I wrong about that?

The macro BOOST_THROW_EXCEPTION did not exist prior to Boost Exception. It
was introduced so that the __FILE__ and __LINE__ of the throw are captured
in the exception object. This new functionality does not depend on the
Boost Exception submodule.

You should look at how the git submodules are structured:
boost/throw_exception.hpp is in its own minimodule which also includes


Boost list run by bdawes at, gregod at, cpdaniel at, john at