Update links in the iterator library. I haven't regenerated the documentation, but the changes should be in sync with the source files.

[SVN r41660]
This commit is contained in:
Daniel James
2007-12-03 20:08:14 +00:00
parent a2f779bfbe
commit b4ee8ac96d
6 changed files with 9 additions and 9 deletions
+2 -2
View File
@@ -40,7 +40,7 @@ Lab</a>, <a class="reference external" href="http://www.styleadvisor.com">Zephyr
<col class="field-body" />
<tbody valign="top">
<tr class="field"><th class="field-name">Abstract:</th><td class="field-body">The Boost Iterator Library contains two parts. The first
is a system of <a class="reference external" href="../../../more/generic_programming.html#concept">concepts</a> which extend the C++ standard
is a system of <a class="reference external" href="http://beta.boost.org/community/generic_programming.html#concept">concepts</a> which extend the C++ standard
iterator requirements. The second is a framework of
components for building iterators based on these
extended concepts and includes several useful iterator
@@ -179,7 +179,7 @@ implement iterators, you probably wrote a <tt class="docutils literal"><span cla
captures the core operations of your iterator. In the new library
design, you'll move those same core operations into the body of the
iterator class itself. If you were writing a family of iterators,
you probably wrote a <a class="reference external" href="../../../more/generic_programming.html#type_generator">type generator</a> to build the
you probably wrote a <a class="reference external" href="http://beta.boost.org/community/generic_programming.html#type_generator">type generator</a> to build the
<tt class="docutils literal"><span class="pre">iterator_adaptor</span></tt> specialization you needed; in the new library
design you don't need a type generator (though may want to keep it
around as a compatibility aid for older code) because, due to the