16 Oct
2015
16 Oct
'15
5:31 a.m.
Edward Diener-3 wrote
Similarly if any other library depending on 'iterator' needs these changes on 'master' it needs to be co-ordinated with 'iterator'.
Sorry for causing so much trouble! I think Boost.Range was the only library that broke because it depended on boost/iterator/iterator_concepts.hpp including boost/detail/iterator.hpp. Unfortunately that affected other libraries depending on Boost.Range. Marcel -- View this message in context: http://boost.2283326.n4.nabble.com/iterator-range-Synchronization-on-master-... Sent from the Boost - Dev mailing list archive at Nabble.com.