#1614 closed Bugs (fixed)
vector workaround needed for MSVC10
| Reported by: | François Barel | Owned by: | Joel de Guzman |
|---|---|---|---|
| Milestone: | Boost 1.43.0 | Component: | fusion |
| Version: | Boost Development Trunk | Severity: | Problem |
| Keywords: | MSVC VC10 vector | Cc: | frabar666@… |
Description
Hi,
It seems the vector constructor workaround used for MSVC8 and earlier (ctor_helper in boost/fusion/container/vector/vector.hpp) is also required for MSVC9 RTM.
Unfortunately I don't have a simple test case ready. My observation is simply that my Spirit2 parser (using fusion tuples and vectors as rule attributes) doesn't compile on VC9 unless I enable that workaround with the attached patch.
Cheers,
François
Attachments (1)
Change History (8)
by , 15 years ago
| Attachment: | fusion-MSVC9.diff added |
|---|
follow-up: 2 comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Cc: | added |
|---|
Yes, this patch is still needed. Please see http://www.nabble.com/-phoenix2--Compilation-error-with-operator!-td22203420.html for a repro by Sergei Politov.
comment:3 by , 13 years ago
[Bug Sprint]
Confirming that the referenced code fails on MSVC9 SP1 with boost trunk and that the attached patch fixes the problem. I spent some time trying to boil the test code down to a fusion-only test case but failed.
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:5 by , 13 years ago
| Keywords: | VC10 added; VC9 removed |
|---|---|
| Milestone: | Boost 1.36.0 → Boost 1.43.0 |
| Resolution: | fixed |
| Status: | closed → reopened |
| Summary: | vector workaround needed for MSVC9 → vector workaround needed for MSVC10 |
According to the post @ http://article.gmane.org/gmane.comp.lib.boost.devel/203066, this same issue effects the RTM version of VC10.
Fix is to alter the workarounds mentioned in the VC9 patch to check BOOST_MSVC against 1600 instead of 1500.
[Bug Sprint]
Boost trunk still uses #if BOOST_WORKAROUND(BOOST_MSVC, <= 1400), so this patch has not been applied. Is it still needed?