boost_mirror/iterator
1
0
Fork 0
mirror of https://github.com/boostorg/iterator.git synced 2025-05-09 23:23:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

hierarchy->group

Browse Source 
[SVN r20155]
This commit is contained in:
Jeremy Siek 2003-09-22 16:04:44 +00:00
parent 5efcabf3bd
commit d68ac3db4c
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/new-iter-concepts.html
View File

@ -235,8 +235,8 @@ Bidirectional Iterator (2) -> Bidirectional Traversal Iterator and Writable I
</div>
<div class="section" id="design">
<h1><a class="toc-backref" href="#id3" name="design">Design</a></h1>
<p>The iterator requirements are to be separated into two hierarchies. One
set of concepts handles the syntax and semantics of value access:</p>
<p>The iterator requirements are to be separated into two groups. One set
of concepts handles the syntax and semantics of value access:</p>
<ul class="simple">
<li>Readable Iterator</li>
<li>Writable Iterator</li>
@ -276,8 +276,8 @@ but instead use the equivalent of a bitfield.</p>
<p>We provide an access mechanism for mapping iterator types to the new
traversal tags and access bitfield. Our design reuses
<tt class="literal"><span class="pre">iterator_traits&lt;Iter&gt;::iterator_category</span></tt> as the access
mechanism. To that end, a pair of access and traversal tags are
combined into a single type using the following <cite>iterator_tag</cite> class.</p>
mechanism. To that end, the access and traversal information is
bundled into a single type using the following <cite>iterator_tag</cite> class.</p>
<pre class="literal-block">
enum iterator_access { readable_iterator = 1, writable_iterator = 2,
swappable_iterator = 4, lvalue_iterator = 8 };

8
doc/new-iter-concepts.rst
View File

@ -208,8 +208,8 @@ Input Iterator (2) -> Incrementable Iterator and Readable Iterator
Design
========
The iterator requirements are to be separated into two hierarchies. One
set of concepts handles the syntax and semantics of value access:
The iterator requirements are to be separated into two groups. One set
of concepts handles the syntax and semantics of value access:
- Readable Iterator
- Writable Iterator
@ -256,8 +256,8 @@ but instead use the equivalent of a bitfield.
We provide an access mechanism for mapping iterator types to the new
traversal tags and access bitfield. Our design reuses
``iterator_traits<Iter>::iterator_category`` as the access
mechanism. To that end, a pair of access and traversal tags are
combined into a single type using the following `iterator_tag` class.
mechanism. To that end, the access and traversal information is
bundled into a single type using the following `iterator_tag` class.
::