From b81435f4aa08ef02b256115044b1ac8ba041f047 Mon Sep 17 00:00:00 2001 From: Raoul Gough Date: Mon, 20 Oct 2003 16:22:54 +0000 Subject: [PATCH] Force has_mutable_ref to false in set_traits, in case iterator_traits wrong [SVN r20429] --- .../boost/python/suite/indexing/container_traits.hpp | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/include/boost/python/suite/indexing/container_traits.hpp b/include/boost/python/suite/indexing/container_traits.hpp index 2d304c43..7bcf0828 100755 --- a/include/boost/python/suite/indexing/container_traits.hpp +++ b/include/boost/python/suite/indexing/container_traits.hpp @@ -157,10 +157,13 @@ namespace boost { namespace python { namespace indexing { typedef typename boost::call_traits::param_type index_param; BOOST_STATIC_CONSTANT (IndexStyle, index_style = index_style_nonlinear); - BOOST_STATIC_CONSTANT (bool, has_find = true); - BOOST_STATIC_CONSTANT (bool, is_reorderable = false); - // MSVC seems to have a mutable std::set::reference, so we need - // to explicitly cancel is_reorderable here + BOOST_STATIC_CONSTANT (bool, has_find = true); + + BOOST_STATIC_CONSTANT (bool, has_mutable_ref = false); + BOOST_STATIC_CONSTANT (bool, is_reorderable = false); + // Some compilers seem to deduce has_mutable_ref as true from the + // set iterator traits. The previous two constants explicitly hide + // the bad results of that. }; /////////////////////////////////////////////////////////////////////////