Apply changes required by MSVC-15.5. #198
Conversation
…+14 or later mode.
…est /permissive-.
|
By default (that is, without |
|
I thought /permissive- was the default for all new projects? The appveyor tests pass. In any case we need a solution, and I don't see an easy one as there appears to be no way of detecting /permissive- ? I do note that nothing in Boost is using BOOST_NO_TWO_PHASE_NAME_LOOKUP at present so maybe this is moot? |
|
New IDE projects are one thing, but in this way you're going to get test failures in the matrix. Appveyor passes because you test with |
15.5? |
…KUP as we can't tell if /permissive- is in effect or not.
test/config_info.cpp
Outdated
| PRINT_MACRO(_DLL); | ||
| PRINT_MACRO(_ISO_VOLATIL); |
There was a problem hiding this comment.
Typo? Shouldn't this be _ISO_VOLATILE?
|
Just out of curiosity, did my replies to your comments (thanks!) come though, or has Github junked them as I don't see them here? |
|
Mine? I saw commits but no replies I think.
|
|
BTW, is this targeted for 1.66.0, 1.66.1 or 1.67?
|
OK, not getting through then :(
Whatever comes after 1.66... |
|
As Microsoft seems to release new compiler versions in much shorter intervals now, are there any ideas yet, how this can be covered by Boost releases? Are there any workarounds documented for Boost users to overcome the "Unknown compiler" messages, while there is no Boost release, which covers this? |
|
It should say in the warning message, "Define BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE to suppress this message". |
|
@danieljames it doesn't, but thanks for the info. I'lll check it out. |
|
Sorry, that message is added in the new release, coming soon hopefully. |
No description provided.