Added a test for pointee
Fixed iterator_facade so operator[] result type computation didn't
cause a problem with abstract types.
Updated iterator_facade operator[] docs for accuracy.
Allowed Borland to simply fail the indirect_iterator_member_types test
because of its lame const-dropping, instead of trying to work around
it.
[SVN r21579]
is_incrementable.hpp: checks whether ++x is well-formed
pointee.hpp: value_type of iterators or smart pointers
indirect_reference.hpp: reference type of iterators or smart pointers
indirect_iterator.hpp
indirect_iterator_member_types.cpp
Use pointee/indirect_reference to select value/reference type.
iterator_concepts.hpp: Fixed interoperable test. Hardly tests enough, but it's a start
minimum_category.hpp: Better error messages for vc6
indirect_iterator_test.cpp: Workarounds for compilers without SFINAE
static_assert_same.hpp: Informative error reports; added a macro.
zip_iterator_test.hpp: Added missing #include
Jamfile: made zip_iterator test pass with vc6/stlport
[SVN r21514]
- The logic for determining the result of iterator_facade::operator[] has been factored out into a separate detail header in preparation for its potential use in iterator_range to avoid iterator_range::operator[] from returning a reference to a temporary.
[SVN r80901]
- Update iterator_facade test for #1019
(header change already merged).
- Category of each iterator is reduced to a known category before we try to
find a minimum. Fixes#1517.
- `function_input_iterator` from Dean Michael Berris. Fixes#2893
- Fix typo in `boost/iterator.hpp`. Fixes#3434.
- Always include `add_reference` header in iterator adaptor header.
Did not merge changes for #1427.
[SVN r70709]
either changing assert(...) or BOOST_ASSERT(...) to BOOST_TEST
(in my code only)
or adding "return boost::report_errors();" where it was clearly
missing (and a pure bug, in anyone's code).
or changing BOOST_TEST to BOOST_CHECK where the integer library
was clearly using Boost.Test and not returning report_errors().
[SVN r37063]
