Re: [boost] [exception][range] boost/range/size_type.hpp + unexpected dependenciies Exeception -> Units -> Algorithms -> Range -> Concepts

On Wed, Sep 18, 2013 at 1:38 AM, Emil Dotchevski wrote:

On Tue, Sep 17, 2013 at 2:06 PM, Andrey Semashev wrote:

...

On Tuesday 17 September 2013 13:51:02 Emil Dotchevski wrote:

...

On Tue, Sep 17, 2013 at 1:08 PM, Vicente J. Botet Escriba

wrote:

...

What is more surprising is the chain of dependencies the inclusion of

boost/exception_ptr.hpp conveys.

Exeception -> Units -> Algorithms -> Range -> Concepts.

Is there a way to break these dependencies?

Thanks for pointing this out. This is being included by exception_ptr only for the demangle function. If this doesn't get resolved soon I'll scrap the demangling call and remove the dependency.

I recently proposed to extract my type_info_wrapper [1] to Boost.Utility. It has support for name demangling. Maybe you could switch to it (after the extraction, of course) instead of Boost.Units?

Oh, wait. I think I confused Units and Utility. :)

I'll take a look.

Hi again, I can see you've disabled type demangling in 1.55 release to remove the dependency. I really liked that feature, it made my logs more readable. Would you consider re-enabling it if the demangling function is implemented in a separate header in boost/detail? There would be no dependency on Boost.Units and in fact Boost.Units and my own code in Boost.Log could be ported to it as well. PS: The recently reviewed Boost.TypeIndex library will have similar code as well, and it can be converted to use that code too. I really hope that library gets accepted soon, so my plans of extracting type_info_wrapper to Boost.Utility are currently on hold.