Boost C++ Libraries: Ticket #3020: warning using boost::variant

attachment set

Tue, 12 May 2009 21:24:50 GMT

attachment → a.cpp

owner, component changed

Tue, 12 May 2009 21:25:48 GMT

owner changed from Hartmut Kaiser to ebf
component wave → variant

Steven Watanabe — Sun, 17 May 2009 03:24:22 GMT

You can safely ignore this warning. Basically, the compiler is issuing a warning because it is compliant, where previous versions of msvc were not.

Tue, 19 May 2009 20:40:07 GMT

Thanks for clarifying that the code is functional.

Is there a possibility that the boost header will either suppress or avoid the warning in a later release?

Steven Watanabe — Tue, 19 May 2009 21:37:57 GMT

I believe that VC9 doesn't generate this warning. It's unlikely to be suppressed in Boost in the near future, since warnings usually get low priority.

status changed; resolution set

Steven Watanabe — Thu, 10 Jun 2010 14:37:16 GMT

status new → closed
resolution → wontfix

Mon, 07 Mar 2011 22:13:22 GMT

This warning does show up in vc10. Solution would be to add a

#ifdef _MSC_VER
#pragma warning( push )
#pragma warning( disable : 4345 )
#endif

at the top of variant.hpp and

#ifdef _MSC_VER
#pragma warning( pop )
#endif

at the bottom.

status, version, milestone changed; resolution deleted

Michael Caisse — Wed, 07 Dec 2011 01:52:01 GMT

status closed → reopened
version Boost 1.36.0 → Boost 1.48.0
resolution wontfix
milestone Boost 1.40.0 → To Be Determined

Please see David Sankel's comment:6 above.

Problem has resurfaced in VC10. Just love warnings letting me know that they are doing the right thing.

Antony Polukhin — Thu, 26 Sep 2013 07:46:26 GMT

(In [85928]) Fix MSVC warning in Boost.Variant (refs #3020)

owner, status changed

Antony Polukhin — Thu, 26 Sep 2013 07:46:51 GMT

owner changed from ebf to Antony Polukhin
status reopened → new

status, milestone changed; resolution set

Antony Polukhin — Mon, 18 Nov 2013 11:53:54 GMT

status new → closed
resolution → fixed
milestone To Be Determined → Boost 1.56.0

In [86650] fix for this issue was merged to release branch.