feedc0de/boost_iterator
1
0
Fork 0
forked from boostorg/iterator
Code Pull Requests Activity

blah

Browse Source 
[SVN r209]
This commit is contained in:
Jeremy Siek
2002-06-04 20:52:11 +00:00
parent 5a0e943068
commit 8e189aeb49
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/iterator-categories.html
View File

@@ -39,9 +39,9 @@ iterator categories.
<P>Because of the mixing of iterator traversal and dereference return type, many <P>Because of the mixing of iterator traversal and dereference return type, many
useful iterators can not be appropriately categorized. For example, useful iterators can not be appropriately categorized. For example,
<TT>vector&lt;bool&gt;::iterator</TT> is almost a random access iterator, but <TT>vector&lt;bool&gt;::iterator</TT> is almost a random access iterator, but
the return type is not <TT>bool&amp;</TT> (see <A the return type is not <TT>bool&amp;</TT> (see
href="http://anubis.dkuug.dk/JTC1/SC22/WG21/docs/lwg-active.html#96">issue <a href="http://anubis.dkuug.dk/JTC1/SC22/WG21/docs/lwg-active.html#96">issue 96</a>
96</A> and Herb Sutter's paper J16/99-0008 = WG21 N1185). Therefore, the and Herb Sutter's paper J16/99-0008 = WG21 N1185). Therefore, the
iterators only meet the requirements of input iterator and output iterator. This iterators only meet the requirements of input iterator and output iterator. This
is so nonintuitive that at least one implementation erroneously assigns is so nonintuitive that at least one implementation erroneously assigns
<TT>random_access_iterator_tag</TT> as its <TT>iterator_category</TT>. Also, <TT>random_access_iterator_tag</TT> as its <TT>iterator_category</TT>. Also,