Re: [boost] [Range] breaking update pending

From: MB (mb2act_at_[hidden])
Date: 2006-01-30 16:29:24

David Abrahams wrote:
> MB <mb2act_at_[hidden]> writes:
> 
> 
>>Thorsten Ottosen wrote:
>>
>>>Dear All,
>>>
>>>I have been trimming boost.range to incorporate the changes we have been
>>>discussing some time ago.
>>>
>>>These changes will break many uses of the library. Inside boost this 
>>>will affect
>>>
>>>Boost.foreach
>>>Boost.string algo
>>>Boost.iostreams (*)
>>>
>>>(*) I don't this will break
>>>
>>>The list of major changes is the follwing:
>>>
>>>1. ADL hooks renamed boost_range_begin -> range_begin,
>>>                      boost_range_end -> range_end
>>
>>Why was such short name accepted??
>>Even 'const_begin' that calls unqualified 'begin' breaks down Boost.MPL!!
> 
> 
> How so?  What happens?  Got a small reproducible case?

See:
   http://lists.boost.org/boost-users/2006/01/16513.php

   void trouble()
   {
        typedef dummy< ::boost::mpl::vector< int > > vt ;
        typedef ::std::vector< const vt* > ct ;

        boost::const_begin( ct() ) ;
   }

(though I don't know whether or not this GCC behavior is conforming.)

Regards,
MB