Eric Niebler <eric <at> boost-consulting.com> writes:
Thorsten Ottosen wrote:
what about a BOOST_REVERSE_FOREACH ?
Hey, the formal review hasn't started yet! Actually, I don't think BOOST_REVERSE_FOREACH is the right way to approach this. I'd rather see this done with range adaptors:
BOOST_FOREACH( int i, adaptor::reverse(vect) ) { }
... where adaptor::reverse() returns an iterator_range<> (from Boost.Range) of reverse_iterator<> (from Boost.Iterator).
yeah, right, seems better.
I'm working on a set of range adaptors, which I hope to add to boost-sandbox after Christmas. This would be a separate library from BOOST_FOREACH, but it would work well with it.
ok, be sure to check with John Torjo to see if you don't overlap too much in functionality with his range adaptors. If there is filter_iterator, then he has a filter_range and a filtered() function etc. -Thorsten