https://svn.boost.org/trac10/ticket/10269 <p> Boost.Range defines most of its symbols in the boost:: namespace. This introduces conflicts with other Boost libraries, for example: </p> <p> <a class="ext-link" href="http://thread.gmane.org/gmane.comp.lib.boost.devel/249985/focus=249986"><span class="icon">​</span>http://thread.gmane.org/gmane.comp.lib.boost.devel/249985/focus=249986</a> <a class="ext-link" href="http://lists.boost.org/Archives/boost/2014/07/215581.php"><span class="icon">​</span>http://lists.boost.org/Archives/boost/2014/07/215581.php</a> </p> <p> Another drawback is that in user's code unqualified function calls with range arguments use boost:: namespace for symbol lookup, which may introduce unexpected results. </p> <p> I propose to move all Boost.Range symbols to a dedicated namespace (e.g. boost::ranges). For backward compatibility the library can import all public interfaces except operators to the boost:: namespace. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10269 Trac 1.4.3