When using the -Wundef flag with gcc, I get warnings like the following: error: "BOOST_MSVC" is not defined At least once before this was brought up on the lists: http://lists.boost.org/boost-users/2006/10/22819.php The suggested solution is to disable this warning. However, it seems to make more sense to just fix this in Boost (using #if defined(...) or #ifdef). Why not make this fix in Boost? -- Yang Zhang http://www.mit.edu/~y_z/
Yang Zhang wrote:
When using the -Wundef flag with gcc, I get warnings like the following:
error: "BOOST_MSVC" is not defined
At least once before this was brought up on the lists:
http://lists.boost.org/boost-users/2006/10/22819.php
The suggested solution is to disable this warning. However, it seems to make more sense to just fix this in Boost (using #if defined(...) or #ifdef). Why not make this fix in Boost?
Which Boost version, and which headers? We did fix this where BOOST_WORKAROUND is used hence the question. John.
John Maddock wrote:
Yang Zhang wrote:
When using the -Wundef flag with gcc, I get warnings like the following: error: "BOOST_MSVC" is not defined
At least once before this was brought up on the lists:
http://lists.boost.org/boost-users/2006/10/22819.php
The suggested solution is to disable this warning. However, it seems to make more sense to just fix this in Boost (using #if defined(...) or #ifdef). Why not make this fix in Boost?
Which Boost version, and which headers?
We did fix this where BOOST_WORKAROUND is used hence the question.
John. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
boost 1.35, boost/foreach.hpp -- Yang Zhang http://www.mit.edu/~y_z/
Yang Zhang wrote:
John Maddock wrote:
Yang Zhang wrote:
When using the -Wundef flag with gcc, I get warnings like the following: error: "BOOST_MSVC" is not defined
At least once before this was brought up on the lists:
http://lists.boost.org/boost-users/2006/10/22819.php
The suggested solution is to disable this warning. However, it seems to make more sense to just fix this in Boost (using #if defined(...) or #ifdef). Why not make this fix in Boost?
Which Boost version, and which headers?
We did fix this where BOOST_WORKAROUND is used hence the question.
John. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
boost 1.35, boost/foreach.hpp
Just installed boost 1.37. /opt/armed/include/boost/iterator/iterator_facade.hpp:117:1: warning: "BOOST_RWSTD_VER_WORKAROUND_GUARD" is not defined /opt/armed/include/boost/iterator/iterator_facade.hpp:117:1: warning: "BOOST_RWSTD_VER" is not defined /opt/armed/include/boost/iterator/iterator_adaptor.hpp:28:1: warning: "__CODEGEARC___WORKAROUND_GUARD" is not defined /opt/armed/include/boost/iterator/iterator_adaptor.hpp:28:1: warning: "__CODEGEARC__" is not defined /opt/armed/include/boost/function/function_fwd.hpp:24:7: warning: "BOOST_STRICT_CONFIG" is not defined -- Yang Zhang http://www.mit.edu/~y_z/
Yang Zhang wrote:
Just installed boost 1.37.
/opt/armed/include/boost/iterator/iterator_facade.hpp:117:1: warning: "BOOST_RWSTD_VER_WORKAROUND_GUARD" is not defined /opt/armed/include/boost/iterator/iterator_facade.hpp:117:1: warning: "BOOST_RWSTD_VER" is not defined
/opt/armed/include/boost/iterator/iterator_adaptor.hpp:28:1: warning: "__CODEGEARC___WORKAROUND_GUARD" is not defined /opt/armed/include/boost/iterator/iterator_adaptor.hpp:28:1: warning: "__CODEGEARC__" is not defined
/opt/armed/include/boost/function/function_fwd.hpp:24:7: warning: "BOOST_STRICT_CONFIG" is not defined
Now fixed in SVN Trunk, ping me again if you find any more -Wundef warnings from BOOST_WORKAROUND. John.
participants (2)
-
John Maddock -
Yang Zhang