Boost C++ Libraries: Ticket #3106: wave on VS2010 beta compiler generates error

status changed; resolution set

Hartmut Kaiser — Sat, 30 May 2009 13:07:47 GMT

status new → closed
resolution → fixed

(In [53455]) Wave: fixed compilation problems on VC10 beta 1 (fixes #3106)

anthony akentiev — Mon, 01 Jun 2009 07:22:53 GMT

Thank you, Hartmut!

status, version, milestone changed; resolution deleted

Wed, 28 Oct 2009 14:04:42 GMT

status closed → reopened
version Boost 1.39.0 → Boost Development Trunk
resolution fixed
milestone Boost 1.40.0 → Boost 1.42.0

This error is occuring again with VC10 Beta 2.

Changing the previous fix to compare _MSC_FULL_VER with 160021003 instead of 160020506 allows it to compile.

status changed; resolution set

Hartmut Kaiser — Wed, 28 Oct 2009 14:29:06 GMT

status reopened → closed
resolution → fixed

(In [57192]) Wave: fixing compilation for VC10 Beta2 (fixes #3106)

status, milestone changed; resolution deleted

Sat, 13 Feb 2010 10:26:06 GMT

status closed → reopened
resolution fixed
milestone Boost 1.42.0 → Boost 1.43.0

Time for round 3 - it's failing again in the VC10 release candidate.

_MSC_FULL_VER is now 160030128.

status changed; resolution set

Hartmut Kaiser — Sat, 13 Feb 2010 14:46:51 GMT

status reopened → closed
resolution → fixed

(In [59667]) Wave: fixing compilation for VC10 RC (fixes #3106)

status changed; resolution deleted

Wed, 14 Apr 2010 14:53:33 GMT

status closed → reopened
resolution fixed

Hopefully the last time for this!

This problem still occurs in the release version of VC10. _MSC_FULL_VER is 160030319 if that is still needed.

status changed; resolution set

Hartmut Kaiser — Thu, 15 Apr 2010 11:25:59 GMT

status reopened → closed
resolution → fixed

(In [61286]) Wave: fixed #3106: wave on VS2010 beta compiler generates error

Fri, 26 Nov 2010 16:20:38 GMT

By doing a change local to a wave file, anyone trying to use multiindex with vs2010 in a way similar to the way used in wave will face the same issue. I discovered that the hard way... because I have faced the same issue in my code and I found this ticket by googling for a solution ;-)

I believe a special case for vs2010 should be done at a more central location inside boost, setting BOOST_NO_POINTER_TO_MEMBER_TEMPLATE_PARAMETERS for this compiler globally, rather than doing so locally inside wave part. What do you think?

Sebastian Redl — Fri, 26 Nov 2010 16:36:26 GMT

I would like it globally (PropertyTree also needs it). but the macro name is wrong. It's not an issue with member pointers as template parameters - VS2010 is actually perfectly conforming in that it doesn't allow conversions for them (defect in the standard IMO). It's an issue with std::pair, because its members aren't direct members of pair itself. That also means it shouldn't depend on the compiler version, but on the standard library version, as an Intel compiler integrated with VS2010 exhibits the same problem.

So I think the name should be BOOST_NO_DIRECT_PAIR_MEMBERS or something like that.

Fri, 26 Nov 2010 16:43:22 GMT

Your proposal sounds pretty good to me. I'm all for it!