[range] vc7.1 array workaround

Hi, For some msvc-7.1 bug, if you pass an array to boost::begin, a form `range_iterator<const T>` in template< class T > inline BOOST_DEDUCED_TYPENAME range_iterator<const T>::type begin( const T& r ); knocks down the partial specialization system of msvc-7.1. I might find a workaround. See: http://tinyurl.com/yraqje This is msvc-7.1 specific range_iterator. (In fact, any conforming compiler should work. I hope boosters' code review. :-) If this is installed, all the tests compile on msvc-7.1. And all the tests except for iterator_range/sub_range pass. (The two seem to need as_literal etc.) BTW, a redundant assign_detail::assign_decay at <assign/ptr_list_of.hpp> seems to come back in HEAD? Regards, -- Shunsuke Sogame

shunsuke wrote:
Hi,
For some msvc-7.1 bug, if you pass an array to boost::begin, a form `range_iterator<const T>` in
template< class T > inline BOOST_DEDUCED_TYPENAME range_iterator<const T>::type begin( const T& r );
knocks down the partial specialization system of msvc-7.1.
I might find a workaround.
Well, my local complicated tests passed. The patch for range/iterator.hpp has been uploaded. http://svn.boost.org/trac/boost/ticket/1309 Regards, -- Shunsuke Sogame
participants (1)
-
shunsuke