From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-11-27 09:33:29
At 04:29 AM 11/27/2003, Russell Hind wrote:
>John Maddock wrote:
>> Currently it completely messes up the config system because it defines
>> _MSC_VER=1200 (!)
>I ran into this. Basically everywhere there is a workaround for dinkum
>stl and msvc, you also have to check !defined(__BORLANDC__) My initial
>tests with lambda was that basically the new compiler didn't need any
>workarounds but it meant making sure no current workarounds were being
>included for the new version.
Isn't the correct fix usually to change _MSC_VER to BOOST_MSVC?
Other than for the config library, I would really like to ban _MSC_VER
(unless accompanied by a comment that says "// including non-Microsoft
compilers". Otherwise, when you see _MSC_VER in source code, you never know
if the author remembered that compilers other than VC++ define it, and
often with unhelpful values.
Is this something we want to try to fix this release? There is possibly
suspect _MSC_VER use in the Boost headers listed below.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk