I was running into problems with min and max being macros when attempting to port my code to .NET. When I went to look at visualc.hpp, I saw that NOMINMAX was only defined when _MSC_VER <= 1200. My break seems to have happened where a boost file was included, then a windows header came in, so the macros were enabled. I know we are not supposed to rely on Boost.Config in our code, but it sure is nice :). ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------
There are similar problems I also encountered ! My workaround was: add # define BOOST_MSVC _MSC_VER to the config file :-) There are lot of errors I got rid of by using this. "Tom Matelich" <tmatelich@zetec.com> wrote in message news:5790CEEF83581444838043A480BDABD7FD3823@exchange01.zetec.com...
I was running into problems with min and max being macros when attempting to port my code to .NET. When I went to look at visualc.hpp, I saw that NOMINMAX was only defined when _MSC_VER <= 1200. My break seems to have happened where a boost file was included, then a windows header came in, so the macros were enabled.
I know we are not supposed to rely on Boost.Config in our code, but it sure is nice :).
----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------
I was running into problems with min and max being macros when attempting to port my code to .NET. When I went to look at visualc.hpp, I saw that NOMINMAX was only defined when _MSC_VER <= 1200. My break seems to have happened where a boost file was included, then a windows header came in, so the macros were enabled.
Does anyone know why we disabled the workaround for VC7 in the first place? John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm
I was running into problems with min and max being macros when attempting to port my code to .NET. When I went to look at visualc.hpp, I saw that NOMINMAX was only defined when _MSC_VER <= 1200. My break seems to have happened where a boost file was included, then a windows header came in, so the macros were enabled.
I know we are not supposed to rely on Boost.Config in our code, but it sure is nice :).
I've modified the config system so that NOMINMAX is defined in the win32 platform configuration rather than for VC6 specifically, likewise the undefs for min and max are in there now as well, hopefully this won't break anything ... :-) John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm
participants (2)
-
Barnali -
John Maddock -
Tom Matelich