Re: [boost] [modularization] Dependency to Boost.Exceptionunavoidable?

Subject: Re: [boost] [modularization] Dependency to Boost.Exceptionunavoidable?
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2013-11-05 17:17:45

On Tue, Nov 5, 2013 at 2:01 PM, Vicente J. Botet Escriba
<vicente.botet_at_[hidden]> wrote:
> Le 04/11/13 20:22, Emil Dotchevski a écrit :
>>
>> On Mon, Nov 4, 2013 at 12:53 AM, Ahmed Charles <acharles_at_[hidden]>
>> wrote:
>>>
>>> What about combining throw_exception.hpp and exception.hpp and move that
>>> header to config, since it won't depend on anything else and only really
>>> does configuration anyways? Note, if you don't like config as a choice, the
>>> new version of detail which only depends on config sounds nice as well.
>>
>> Logically, it makes sense to keep the two headers but yes, I agree
>> that config is the right module for both boost/throw_exception.hpp and
>> boost/exception/exception.hpp. At any rate this won't introduce any
>> dependencies because boost/throw_exception.hpp depends only on config.
>>
> Even if  boost/exception/exception.hpp doesn't includes boost/shared_ptr.h
> doesn't it depends on Boost.SmartPtr?

Nope, boost/exception/exception.hpp does not depend on anything at all
in any way whatsoever. :)

-- 
Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode