Namespace conflict in implementation of Boost.Integer

[Daryle Walker]

This is based off the thread starting at <​http://lists.boost.org/Archives/boost/2008/07/139840.php>.

In "[source:trunk/boost/integer.hpp@47408 boost/integer.hpp]", class templates in the boost::detail namespace refer to an unadorned integer_traits template. The template referenced is meant to be boost::integer_traits in "[source:trunk/boost/boost/integer_traits.hpp@32576 boost/integer_traits.hpp]". However, a boost::detail::integer_traits template exists in "[source:trunk/boost/boost/detail/numeric_traits.hpp@24446 boost/detail/numeric_traits.hpp]". This latter template gets priority as the choice of what the unadorned integer_traits mention refers to, which was not intended. The problem only manifests when "boost/detail/numeric_traits.hpp" gets #included, directly or indirectly, before "boost/integer.hpp", but doesn't manifest if "boost/integer.hpp" is #included first (which may be a ODR violation).

Thanks to Jeroen van der Wulp for initially reporting this and providing a potential patch.

[Daryle Walker]

Potential patch provided by Jeroen van der Wulp

[Daryle Walker]

(In [47742]) Resolved namespace conflict from unadorned call, which fixes #2134

[anonymous]

Recent Trunk reversion has broken this - or rather it hasn't because Boost.Integer is no longer hiding it's details in the detail namespace - and it should.

[John Maddock]

(In [57884]) Tidied up namespace usage, fixes #2134.