Cleaned up and normalized HTML fragment anchors in the DRM. Moved some around so

they refer to the correct text. Changed many to mark the relevant text within
the anchor tag instead of using empty tags. Fixed some broken cross-reference
links.

Author: cbpage

Arithmetic_Operations.html

@@ -1099,8 +1099,8 @@ <h5 class="method-signature"><span class="signature"><code><var>complex</var> ^
       <a name="HEADING-100-179"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1653">abs</code> </span><span class="attributes-summary">[Open Generic Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1654"></a>Returns the absolute value of its
-	argument.</p>
+      <p class="short-description"><a name="XREF-1654">Returns the absolute value of its
+	argument.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1173,8 +1173,8 @@ <h4 class="item-title"><span class="signature"><a name="IX-1657"></a><code id="I
       <a name="HEADING-100-193"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1658">logxor</code> </span><span class="attributes-summary">[Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1659"></a>Returns the bitwise exclusive or of
-	its integer arguments.</p>
+      <p class="short-description"><a name="XREF-1659">Returns the bitwise exclusive or of
+	its integer arguments.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1207,8 +1207,8 @@ <h4 class="item-title"><span class="signature"><code id="IX-1658">logxor</code>
       <a name="HEADING-100-199"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1660">logand</code> </span><span class="attributes-summary">[Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1661"></a>Returns the bitwise and of its
-	integer arguments.</p>
+      <p class="short-description"><a name="XREF-1661">Returns the bitwise and of its
+	integer arguments.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1241,8 +1241,8 @@ <h4 class="item-title"><span class="signature"><code id="IX-1660">logand</code>
       <a name="HEADING-100-205"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1662">lognot</code> </span><span class="attributes-summary">[Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1663"></a>Returns the bitwise not of its
-	integer argument.</p>
+      <p class="short-description"><a name="XREF-1663">Returns the bitwise not of its
+	integer argument.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1275,8 +1275,8 @@ <h4 class="item-title"><span class="signature"><code id="IX-1662">lognot</code>
       <a name="HEADING-100-211"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1664">logbit?</code> </span><span class="attributes-summary">[Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1665"></a>Tests the value of a particular bit
-	in its integer argument.</p>
+      <p class="short-description"><a name="XREF-1665">Tests the value of a particular bit
+	in its integer argument.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1315,8 +1315,8 @@ <h4 class="item-title"><span class="signature"><code id="IX-1664">logbit?</code>
       <a name="HEADING-100-219"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1666">ash</code> </span><span class="attributes-summary">[Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1667"></a>Performs an arithmetic shift on its
-	first argument.</p>
+      <p class="short-description"><a name="XREF-1667">Performs an arithmetic shift on its
+	first argument.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1366,8 +1366,8 @@ <h4 class="item-title"><span class="signature"><code id="IX-1666">ash</code> </s
       <a name="HEADING-100-230"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1669">lcm</code> </span><span class="attributes-summary">[Open Generic Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1670"></a>Returns the least common multiple of
-	its two arguments.</p>
+      <p class="short-description"><a name="XREF-1670">Returns the least common multiple of
+	its two arguments.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>
@@ -1407,8 +1407,8 @@ <h5 class="method-signature"><span class="signature"><code>lcm <var>integer1 int
       <a name="HEADING-100-239"></a>
       <h4 class="item-title"><span class="signature"><code id="IX-1671">gcd</code> </span><span class="attributes-summary">[Open Generic Function]</span></h4>
       <hr class="item-title" />
-      <p class="short-description"><a name="XREF-1672"></a>Returns the greatest common divisor
-	of its two arguments.</p>
+      <p class="short-description"><a name="XREF-1672">Returns the greatest common divisor
+	of its two arguments.</a></p>
       <dl class="Cliche">
 	<dt><span>Signature:</span></dt>
 	<dd>

Assignment.html

@@ -148,10 +148,10 @@ <h1 class="section-title"><a name="IX-451">Assignment</a></h1>
 <code> &rArr;</code>  110
 *foo*
 <code> &rArr;</code>  110</pre>
-      <p><a name="IX-454"></a><a name="IX-455"></a>The following examples show the use
-	of <code>:=</code> as shorthand for calling a setter function. In general, using this syntax to
-	call a function <var>fun</var> is equivalent to calling the
-	function <code><var>fun</var>-setter</code>.</p>
+      <p>The following examples show the use of <code>:=</code> as <a name="IX-454">shorthand for
+	calling a setter function</a>. In general, using this syntax to call a
+	function <var>fun</var> is equivalent to calling the
+	function <a name="IX-455"><code><var>fun</var>-setter</code></a>.</p>
       <pre class="code">
 define variable *foo* = vector (10, 6, 8, 5);
 element(*foo*, 2)

Auxiliary_Rule_Sets.html

@@ -133,14 +133,13 @@
 
       <a name="HEADING-84-0"></a>
       <a name="UID-Macros-1862"></a>
-      <h1 class="section-title">Auxiliary Rule Sets</h1>
-      <p><a name="IX-1265"></a>Auxiliary rule sets are
-	like <a name="IX-1266"></a>subroutines for rewrite rules. An auxiliary rule set
-	rewrites the value of a pattern variable after it is bound by a pattern and before it is
-	substituted into a template. Auxiliary rule sets only come into play after a pattern has
-	matched; the failure of all patterns in an auxiliary rule set to match causes the entire
-	macro call to be declared invalid, rather than back-tracking and trying the next pattern in
-	the calling rule set.</p>
+      <h1 class="section-title"><a name="IX-1265">Auxiliary Rule Sets</a></h1>
+      <p>Auxiliary rule sets are like <a name="IX-1266"></a>subroutines for rewrite rules. An
+	auxiliary rule set rewrites the value of a pattern variable after it is bound by a pattern
+	and before it is substituted into a template. Auxiliary rule sets only come into play after
+	a pattern has matched; the failure of all patterns in an auxiliary rule set to match causes
+	the entire macro call to be declared invalid, rather than back-tracking and trying the next
+	pattern in the calling rule set.</p>
       <p>See the definition of <var>aux-rule-sets</var>
 	in <a href="Phrase_Grammar#XREF-2122"><q>Auxiliary Rule Sets</q> on page 430</a>.</p>
       <p>A <em class="BNFCaps">symbol</em> flags the beginning of an auxiliary rule set. For

BNF.html

@@ -134,7 +134,7 @@ <h1 class="appendix-title"><a name="XREF-2090">BNF</a></h1>
       <h2 class="subsection-title">General Notes</h2>
       <p>Dylan <a name="IX-2091">syntax</a> can be parsed with
 	an <a name="IX-2092">LALR(1)</a> <a name="IX-2093">grammar.</a></p>
-      <p><a name="IX-2094"></a>This appendix uses some special notation to make the
+      <p>This appendix uses some special <a name="IX-2094">notation</a> to make the
 	presentation of the grammar more readable.</p>
       <ul>
 	<li>The <sub class="BNF"><i>opt</i></sub> suffix means that the preceding item is
@@ -169,7 +169,7 @@ <h2 class="subsection-title">General Notes</h2>
 	definitions and case-body). The grammar can be made LALR(1) through well-known standard
 	transformations implemented by most parser generators.</p>
       <a name="HEADING-116-11"></a>
-      <h2 class="subsection-title"><a name="IX-2095"></a>Lexical Notes</h2>
+      <h2 class="subsection-title"><a name="IX-2095">Lexical Notes</a></h2>
       <p>In the lexical grammar, the various elements that come together to form a single token on
 	the right-hand sides of rules must <var>not</var> be separated by whitespace, so that the end
 	result will be a single token. This is in contrast to the phrase grammar, where each element

Background_and_Goals.html

@@ -127,7 +127,7 @@
 
       <a name="HEADING-6-0"></a>
       <a name="UID-Introduction-2118"></a>
-      <h1 class="section-title"><a name="IX-169"></a>Background and Goals</h1>
+      <h1 class="section-title"><a name="IX-169">Background and Goals</a></h1>
       <p>Dylan is a general-purpose, high-level programming language, designed for use in
 	application and systems programming. Dylan includes garbage collection, type-safety, error
 	recovery, a module system, and programmer control over runtime extensibility of

Bindings.html

@@ -151,7 +151,7 @@ <h1 class="section-title">Bindings</h1>
 	initialize or assign the binding to a value that is not of the correct type.</p>
       <p>A binding is either <dfn id="IX-227">constant</dfn>
 	or <dfn id="IX-228">variable</dfn>. A constant
-	(or <a name="IX-229"></a>read-only) binding always has the same value. In contrast, a
+	(or <a name="IX-229">read-only</a>) binding always has the same value. In contrast, a
 	variable (or writable) binding can have its value changed, using the assignment
 	operator <code>:=</code>. Most bindings in a typical Dylan module are constant.</p>
 

Built-In_Classes.html

@@ -131,7 +131,7 @@
 
       <a name="LINK-Built-In_Classes-firstpage"></a><a name="HEADING-87-0"></a>
       <a name="UID-Built-In_Classes-1378"></a>
-      <h1 class="chapter-title"><a name="XREF-1359"></a>The Built-In Classes</h1>
+      <h1 class="chapter-title"><a name="XREF-1359">The Built-In Classes</a></h1>
       <h2 class="chapter-title">Contents</h2>
 
       <ul class="TOC">

Built-In_Classes_Overview.html

@@ -132,9 +132,8 @@
 
       <a name="HEADING-88-0"></a>
       <a name="UID-Built-In_Classes-12650"></a>
-      <h1 class="section-title">Overview</h1>
-      <p><a name="IX-1360"></a>This chapter contains an entry for every class defined by
-	Dylan.</p>
+      <h1 class="section-title"><a name="IX-1360">Overview</a></h1>
+      <p>This chapter contains an entry for every class defined by Dylan.</p>
       <p>The superclasses listed for a class <var>C</var> are those classes defined by the Dylan
 	language from which <var>C</var> most directly inherits. They are not required to be the
 	direct superclasses of <var>C</var>, because implementations are free to insert
@@ -147,10 +146,10 @@ <h1 class="section-title">Overview</h1>
 	free. A class may be specified as instantiable. If it is not, then it is
 	uninstantiable. <a href="Sealing">Chapter 9, <q>Sealing,</q></a> contains a complete
 	description of these characteristics.</p>
-      <p><a name="IX-1361"></a><a name="IX-1362"></a>An implementation may choose to
-	impose fewer restrictions than specified. For example, a class specified as sealed may be
-	left open, and a class specified as primary may be left free. However, any program that
-	takes advantage of this liberality will not be portable.</p>
+      <p><a name="IX-1361"></a>An implementation may choose to impose fewer restrictions than
+	specified. For example, a class specified as sealed may be left open, and a class specified
+	as primary may be left free. However, any program that takes advantage of
+	this <a name="IX-1362">liberality</a> will not be portable.</p>
       <p>Each class entry includes tables of operations defined on the class. These tables are cross
 	references to <a href="Built-In_Functions">Chapter 12, <q>The Built-In Functions,</q></a>
 	and represent redundant information. A function, generic function, or method is listed under

Built-In_Functions.html

@@ -134,7 +134,7 @@
 
       <a name="LINK-Built-In_Functions-firstpage"></a><a name="HEADING-96-0"></a>
       <a name="UID-Built-In_Functions-20426"></a>
-      <h1 class="chapter-title"><a name="XREF-1527"></a>The Built-In Functions</h1>
+      <h1 class="chapter-title"><a name="XREF-1527">The Built-In Functions</a></h1>
       <h2 class="chapter-title">Contents</h2>
 
       <ul class="TOC">

Built-In_Functions_Overview.html

@@ -135,24 +135,23 @@
 
       <a name="HEADING-97-0"></a>
       <a name="UID-Built-In_Functions-20433"></a>
-      <h1 class="section-title">Overview</h1>
-      <p><a name="IX-1528"></a>This chapter contains an entry for each function defined by
-	Dylan.</p>
-      <p><a name="IX-1529"></a>The functions described below are annotated either as
+      <h1 class="section-title"><a name="IX-1528">Overview</a></h1>
+      <p>This chapter contains an entry for each function defined by Dylan.</p>
+      <p>The functions described below are <a name="IX-1529">annotated</a> either as
 	an <q>open generic function</q> or as a <q>function.</q></p>
-      <p>A function specified as an <q><a name="IX-1530"></a>open generic function</q> can be
+      <p>A function specified as an <q><a name="IX-1530">open generic function</a></q> can be
 	extended through the addition of programmer defined methods. The signature of the generic
 	function constrains which methods can be added through the congruency rules described
 	on <a href="Parameter_Lists#XREF-837">page 93</a>. The signature does not imply a set
-	of <a name="IX-1531"></a>predefined methods. For example, the signature
+	of predefined <a name="IX-1531">methods</a>. For example, the signature
 	of <code>+</code> is <code>(&lt;object&gt;, &lt;object&gt;)</code>, but the predefined
 	methods on <code>+</code> only cover subtypes of <code>&lt;number&gt;</code>. Particular
 	behavior of the function is given in its description and in the description of its
 	methods.</p>
       <p><a name="IX-1532"></a>A function specified as a <q>function</q> cannot portably be
 	extended through the addition of methods. Implementations are free to implement these
 	functions as open generic functions, but programs that take advantage of
-	such <a name="IX-1533"></a>liberality will not be portable. The signature of such a
+	such <a name="IX-1533">liberality</a> will not be portable. The signature of such a
 	function specifies the types of the arguments to which the function may be applicable, but
 	does not necessarily imply that the function is applicable to all instances of the
 	types. The exact behavior of the function is given in its description.</p>
@@ -161,7 +160,7 @@ <h1 class="section-title">Overview</h1>
 	this liberality will not be portable.</p>
       <p>When a method is specified, it describes the behavior of a generic function when applied to
 	arguments of particular types. It does not imply that this behavior is implemented by a
-	single method. A method described as <q><a name="IX-1534"></a>sealed</q> specifies a
+	single method. A method described as <q><a name="IX-1534">sealed</a></q> specifies a
 	sealed domain covering the generic function and specializers of the method.</p>
       <p>Where a sealed domain is specified, implementations are free to seal the domain or leave
 	the domain unsealed. Portable programs should not rely on the domain being