feedc0de/boost_range
1
0
Fork 0
forked from boostorg/range
Code Pull Requests Activity

fixed broken links

Browse Source 
[SVN r30421]
This commit is contained in:
Jonathan Turkanis
2005-08-03 19:43:36 +00:00
parent d0f9bf8cc0
commit 59f118601a
4 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/intro.html
View File

@@ -46,7 +46,7 @@
null terminated strings, <code>std::pairs</code> of iterators, and raw null terminated strings, <code>std::pairs</code> of iterators, and raw
arrays (and more), such that the same generic code can work with them all. arrays (and more), such that the same generic code can work with them all.
The basic idea is to add another layer of indirection using <a The basic idea is to add another layer of indirection using <a
href="../../mpl/doc/index.html#metafunctions">metafunctions</a> and href="../../mpl/doc/refmanual/metafunction.html">metafunctions</a> and
free-standing functions so syntactic and/or semantic differences can be removed. free-standing functions so syntactic and/or semantic differences can be removed.
</p> </p>
@@ -130,7 +130,7 @@ class=identifier>assign</span><span class=special>( </span><span class=identifie
</blockquote> </blockquote>
By using the free-standing functions and <a By using the free-standing functions and <a
href="../../mpl/doc/index.html#metafunctions">metafunctions</a>, the code automatically href="../../mpl/doc/refmanual/metafunction.html">metafunctions</a>, the code automatically
works for all the types supported by this library; now and in the future. works for all the types supported by this library; now and in the future.
Notice that we have to Notice that we have to
provide two version of <code >find()</code> since we cannot forward a non-const provide two version of <code >find()</code> since we cannot forward a non-const

2
doc/range.html
View File

@@ -81,7 +81,7 @@ category</a> of the underlying iterator type. Therefore
for more information about naming of ranges.</p> for more information about naming of ranges.</p>
<p> The concepts described below specifies associated types as <p> The concepts described below specifies associated types as
<a href="../../mpl/doc/index.html#metafunctions">metafunctions</a> and all <a href="../../mpl/doc/refmanual/metafunction.html">metafunctions</a> and all
functions as free-standing functions to allow for a layer of indirection. </p> functions as free-standing functions to allow for a layer of indirection. </p>
<p><i>Notice that these metafunctions must be defined in namespace </i> <p><i>Notice that these metafunctions must be defined in namespace </i>

2
doc/style.html
View File

@@ -19,7 +19,7 @@
<h2>Terminology and style guidelines </h2> <h2>Terminology and style guidelines </h2>
<p> <p>
The use of a consistent terminology is as important for <a href="range.html#range">Range</a>s The use of a consistent terminology is as important for <a href="range.html">Range</a>s
and range-based algorithms as it is for iterators and iterator-based algorithms. and range-based algorithms as it is for iterators and iterator-based algorithms.
If a conventional set of names are adopted, we can avoid misunderstandings and If a conventional set of names are adopted, we can avoid misunderstandings and
write generic function prototypes that are <i>self-documenting</i>. write generic function prototypes that are <i>self-documenting</i>.

2
index.html
View File

@@ -39,7 +39,7 @@
<li><a href="doc/range.html">Range concepts:</a> <li><a href="doc/range.html">Range concepts:</a>
<ul> <ul>
<li> <a href="doc/range.html#single_pass_range">SinglePassRange</a> <li> <a href="doc/range.html#single_pass_range">SinglePassRange</a>
<li> <a href="doc/range.html#range">ForwardRange</a> <li> <a href="doc/range.html#forward_range">ForwardRange</a>
<li> <a href="doc/range.html#bidirectional_range">BidirectionalRange</a> <li> <a href="doc/range.html#bidirectional_range">BidirectionalRange</a>
<li> <a href="doc/range.html#random_access_range">RandomAccessRange</a> </ul> <li> <a href="doc/range.html#random_access_range">RandomAccessRange</a> </ul>