The following lines are found at the end of boost/iterator/detail/config_def.h : #if BOOST_WORKAROUND(__GNUC__, == 2 && __GNUC_MINOR__ == 95) \ || BOOST_WORKAROUND(__MWERKS__, <= 0x2407) \ || BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x551)) # define BOOST_ITERATOR_NO_MPL_AUX_HAS_XXX // "MPL's has_xxx facility doesn't work" #endif However, I can't find any code using this define - BOOST_ITERATOR_NO_MPL_AUX_HAS_XXX Would it make sense to remove the workaround? -- AlisdairM
"AlisdairM" <alisdair.meredith@uk.renaultf1.com> writes:
The following lines are found at the end of boost/iterator/detail/config_def.h :
#if BOOST_WORKAROUND(__GNUC__, == 2 && __GNUC_MINOR__ == 95) \ || BOOST_WORKAROUND(__MWERKS__, <= 0x2407) \ || BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x551)) # define BOOST_ITERATOR_NO_MPL_AUX_HAS_XXX // "MPL's has_xxx facility doesn't work" #endif
However, I can't find any code using this define - BOOST_ITERATOR_NO_MPL_AUX_HAS_XXX
Would it make sense to remove the workaround?
Sounds right. If you have commit privileges, feel free. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (2)
-
AlisdairM -
David Abrahams