mirror of
https://github.com/boostorg/more.git
synced 2025-03-13 11:40:11 +08:00
Link footnotes back to their location in the document.
[SVN r53613]
This commit is contained in:
parent
79f9bbbb9d
commit
a7458a5c7d
@ -130,7 +130,7 @@
|
||||
<h3><a name="elements" id="elements">Document elements</a></h3>
|
||||
|
||||
<p>Each document contains the following elements, as applicable<a class=
|
||||
"footnote" href="#footnote1">(1)</a>:</p>
|
||||
"footnote" href="#footnote1" id="footnote1-location">(1)</a>:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="#summary">Summary</a></li>
|
||||
@ -204,7 +204,7 @@
|
||||
<p>In some cases the semantic requirements are presented as C++ code. Such
|
||||
code is intended as a specification of equivalance of a construct to
|
||||
another construct, not necessarily as the way the construct must be
|
||||
implemented.<a class="footnote" href="#footnote2">(2)</a></p>
|
||||
implemented.<a class="footnote" href="#footnote2" id="footnote2-location">(2)</a></p>
|
||||
|
||||
<h4><a name="detailed-specs" id="detailed-specs">Detailed
|
||||
specification</a></h4>
|
||||
@ -225,7 +225,7 @@
|
||||
</ul>
|
||||
|
||||
<p>Descriptions of class member functions follow the order (as
|
||||
appropriate)<a class="footnote" href="#footnote3">(3)</a>:</p>
|
||||
appropriate)<a class="footnote" href="#footnote3" id="footnote3-location">(3)</a>:</p>
|
||||
|
||||
<ul>
|
||||
<li>Constructor(s) and destructor</li>
|
||||
@ -243,7 +243,7 @@
|
||||
|
||||
<p>Descriptions of function semantics contain the following <a name=
|
||||
"function-elements" id="function-elements">elements</a> (as
|
||||
appropriate)<a class="footnote" href="#footnote4">(4):</a></p>
|
||||
appropriate)<a class="footnote" href="#footnote4" id="footnote4-location">(4):</a></p>
|
||||
|
||||
<dl class="function-semantics">
|
||||
<dt><b><a href="#requires">Requires:</a></b> the preconditions for
|
||||
@ -425,20 +425,20 @@ void resize(size_type n, charT c);
|
||||
<h2><a name="footnotes" id="footnotes">Footnotes</a></h2>
|
||||
|
||||
<dl>
|
||||
<dt><a class="footnote" name="footnote1" id="footnote1">(1)</a> To save
|
||||
<dt><a class="footnote" id="footnote1" href="#footnote1-location">(1)</a> To save
|
||||
space, items that do not apply to a clause are omitted. For example, if a
|
||||
clause does not specify any requirements, there will be no "Requirements"
|
||||
subclause.</dt>
|
||||
|
||||
<dt><a class="footnote" name="footnote2" id="footnote2">(2)</a> Although
|
||||
<dt><a class="footnote" id="footnote2" href="#footnote2-location">(2)</a> Although
|
||||
in some cases the code is unambiguously the optimum implementation.</dt>
|
||||
|
||||
<dt><a class="footnote" name="footnote3" id="footnote3">(3)</a> To save
|
||||
<dt><a class="footnote" id="footnote3" href="#footnote3-location">(3)</a> To save
|
||||
space, items that do not apply to a class are omitted. For example, if a
|
||||
class does not specify any comparison functions, there will be no
|
||||
"Comparison functions" subclause.</dt>
|
||||
|
||||
<dt><a class="footnote" name="footnote4" id="footnote4">(4)</a> To save
|
||||
<dt><a class="footnote" id="footnote4" href="#footnote4-location">(4)</a> To save
|
||||
space, items that do not apply to a function are omitted. For example, if
|
||||
a function does not specify any precondition, there will be no "Requires"
|
||||
paragraph.</dt>
|
||||
|
Loading…
Reference in New Issue
Block a user