Strip comments and inline ids onto h*

03-06.html

@@ -10,16 +10,9 @@
   <meta name="vspubdate" content="07/01/97" />
   <meta name="vscategory" content="Web and Software Development: Game Development,Web and Software Development: Graphics and Multimedia Development" />
 
-  <title>Michael Abrash's Graphics Programming Black Book Special Edition: Assume Nothing</title><!-- HEADER -->
-  <!-- Empty Reference Subhead -->
-  <!--ISBN=1576101746//-->
-  <!--TITLE=Michael Abrash's Graphics Programming Black Book Special Edition//-->
-  <!--AUTHOR=Michael Abrash//-->
-  <!--PUBLISHER=The Coriolis Group, Inc.//-->
+  <title>Michael Abrash's Graphics Programming Black Book Special Edition: Assume Nothing</title>
   <meta name="chapter" content="03" />
   <meta name="pages" content="051-053" />
-  <!--UNASSIGNED1//-->
-  <!--UNASSIGNED2//-->
 </head>
 
 <body>
@@ -39,7 +32,7 @@
 
   <p>Listing 3.3 is used by naming it TESTCODE, assembling both Listing 3.2 (which includes TESTCODE) and Listing 3.1 with TASM or MASM, and linking the two resulting OBJ files together by way of the Borland orMicrosoft linker. Listing 3.4 shows a batch file, PZTIME.BAT, which does all that; when run, this batch file generates and runs the executable file PZTEST.EXE. PZTIME.BAT (Listing 3.4) assumes that the file PZTIMER.ASM contains Listing 3.1, and the file PZTEST.ASM contains Listing 3.2. The command-line parameter to PZTIME.BAT is the name of the file to be copied to TESTCODE and included into PZTEST.ASM. (Note that Turbo Assembler can be substituted for MASM by replacing &ldquo;masm&rdquo; with &ldquo;tasm&rdquo; and &ldquo;link&rdquo; with &ldquo;tlink&rdquo; in Listing 3.4. The same is true of Listing 3.7.)</p>
 
-  <p><b>LISTING 3.4 PZTIME.BAT</b></p><!-- CODE //-->
+  <p><b>LISTING 3.4 PZTIME.BAT</b></p>
   <pre>
 echo off
 rem
@@ -102,25 +95,25 @@ echo ***************************************************************
 echo * An error occurred while building the precision Zen timer.   *
 echo ***************************************************************
 :end
-</pre><!-- END CODE //-->
+</pre>
 
-  <p>Assuming that Listing 3.3 is named LST3-3.ASM and Listing 3.4 is named PZTIME.BAT, the code in Listing 3.3 would be timed with the command:</p><!-- CODE SNIP //-->
+  <p>Assuming that Listing 3.3 is named LST3-3.ASM and Listing 3.4 is named PZTIME.BAT, the code in Listing 3.3 would be timed with the command:</p>
   <pre>
 pztime LST3-3.ASM
-</pre><!-- END CODE SNIP //-->
+</pre>
 
   <p>which performs all assembly and linking, and reports the execution time of the code in Listing 3.3.</p>
 
   <p>When the above command is executed on an original 4.77 MHz IBM PC, the time reported by the Zen timer is 3619 &micro;s, or about 3.62 &micro;s per load of AL from memory. (While the exact number is 3.619 &micro;s per load of AL, I&rsquo;m going to round off that last digit from now on. No matter how many repetitions of a given instruction are timed, there&rsquo;s just too much noise in the timing process&mdash;between dynamic RAM refresh, the prefetch queue, and the internal state of the processor at the start of timing&mdash;for that last digit to have any significance.) Given the test PC&rsquo;s 4.77 MHz clock, this works out to about 17 cycles per <b>MOV</b>, which is actually a good bit longer than Intel&rsquo;s specified 10-cycle execution time for this instruction. (See the MASM or TASM documentation, or Intel&rsquo;s processor reference manuals, for official execution times.) Fear not, the Zen timer is right&mdash;<b>MOV AL,[MEMVAR]</b> really does take 17 cycles as used in Listing 3.3. Exactly why that is so is just what this book is all about.</p>
 
-  <p>In order to perform any of the timing tests in this book, enter Listing 3.1 and name it PZTIMER.ASM, enter Listing 3.2 and name it PZTEST.ASM, and enter Listing 3.4 and name it PZTIME.BAT. Then simply enter the listing you wish to run into the file <i>filename</i> and enter the command:</p><!-- CODE SNIP //-->
+  <p>In order to perform any of the timing tests in this book, enter Listing 3.1 and name it PZTIMER.ASM, enter Listing 3.2 and name it PZTEST.ASM, and enter Listing 3.4 and name it PZTIME.BAT. Then simply enter the listing you wish to run into the file <i>filename</i> and enter the command:</p>
   <pre>
 pztime &lt;filename&gt;
-</pre><!-- END CODE SNIP //-->
+</pre>
 
   <p>In fact, that&rsquo;s exactly how I timed each of the listings in this book. Code fragments you write yourself can be timed in just the same way. If you wish to time code directly in place in your programs, rather than in the test-bed program of Listing 3.2, simply insert calls to <b>ZTimerOn, ZTimerOff</b>, and <b>ZTimerReport</b> in the appropriate places and link PZTIMER to your program.</p>
 
-  <h3><a id="Heading12"></a>The Long-Period Zen Timer</h3>
+  <h3 id="Heading12">The Long-Period Zen Timer</h3>
 
   <p>With a few exceptions, the Zen timer presented above will serve us well for the remainder of this book since we&rsquo;ll be focusing on relatively short code sequences that generally take much less than 54 ms to execute. Occasionally, however, we will need to time longer intervals. What&rsquo;s more, it is very likely that you will want to time code sequences longer than 54 ms at some point in your programming career. Accordingly, I&rsquo;ve also developed a Zen timer for periods longer than 54 ms. The long-period Zen timer (so named by contrast with the precision Zen timer just presented) shown in Listing 3.5 can measure periods up to one hour in length.</p>
 
@@ -147,10 +140,6 @@ pztime &lt;filename&gt;
 
   <div align="center">
     Graphics Programming Black Book &copy; 2001 Michael Abrash
-  </div><!-- all of the reference materials (books) have the footer and subfoot reveresed -->
-  <!-- reference_subfoot = footer -->
-  <!-- reference_footer = subfoot -->
-  <!-- BEGIN SUB FOOTER -->
-  <!-- END FOOTER -->
+  </div>
 </body>
 </html>