Boost C++ Libraries: Ticket #6323: Conflicting forward declarations with versioned namespace in libstdc++.

status, component changed; owner set

Daniel James — Mon, 02 Jan 2012 09:38:36 GMT

owner set to Daniel James
status new → assigned
component None → hash

Do you know if there's a way to detect when versioned namespaces are used?

pluto@… — Mon, 02 Jan 2012 15:45:53 GMT

the <boost/container/container_fwd.hpp> should include <boost/detail/container_fwd.hpp> which handles BOOST_DETAIL_NO_CONTARINER_FWD macro that can be defined by users in such situation.

Daniel James — Mon, 02 Jan 2012 15:52:18 GMT

I think you're a little confused, <boost/container/container_fwd.hpp> forward declares Boost's own implementation of the containers, not the ones in the std namespace. It's always fine for it to forward declare its own containers.

pluto@… — Mon, 02 Jan 2012 17:49:09 GMT

on the 1.48.0 release the <boost/container/container_fwd.hpp> constains fwd decls for std:: elements and fwd decls for boost's containers and btw this is already fixed on trunk by:

------------------------------------------------------------------------
r76114 | igaztanaga | 2011-12-23 13:00:27 +0100 (Fri, 23 Dec 2011) | 1 line
Changed paths:
   M /trunk/boost/container/container_fwd.hpp
   M /trunk/boost/interprocess/interprocess_fwd.hpp
Bug #6287
------------------------------------------------------------------------

Daniel James — Mon, 02 Jan 2012 17:57:15 GMT

OK, I had a look at the current trunk before writing so I missed that it was changed recently. But that's for #6287 and is irrelevant here anyway. This report is for an error which happens when <boost/detail/container_fwd.hpp> is included - you can see that from the error report. If there's some means by which versioned namespaces can be detected - typically by checking for a macro defined by the gcc standard library - then <boost/detail/container_fwd.hpp> can be changed to do the right thing automatically. Otherwise it'll probably have to be changed to just include all the relevant headers.

Daniel James — Fri, 13 Jan 2012 08:55:35 GMT

(In [76444]) Unordered: Mark up new container forwarding failures. Refs #6323.

A lot of new failures because container forwading is now disabled for a lot of cases where it doesn't have to be.

Daniel James — Fri, 13 Jan 2012 09:00:37 GMT

And previously: (In [76419]) Detail: Disable container forward declarations for recent versions of libstdc++.

status changed; resolution set

Daniel James — Sun, 15 Jan 2012 19:56:15 GMT

status assigned → closed
resolution → fixed

(In [76529]) Detail: Merge disabled gcc container forwardings. Fixes #6323.