|
|
|
|
|
|
|
Hardware speed is decidedly a practical issue in this regard. As an example, one round-trip test of 22 million dates was conducted on a venerable PC/XT and lasted for a bit over 120.6 hours. The same program was run on a Pentium-based PC clone (circa early 1997) and required just under 10 minutes and 14 seconds to run to completion. The speed ratio is therefore approximately one of months versus hours. |
|
|
|
|
|
|
|
|
C.3
Test Program Output by Filename |
|
|
|
|
|
|
|
|
The CD contains the actual output of each test program in the text of the files ch10033a.txt through ch10033j.txt. The association of program to output is the obvious one, with each DTLT_xxx.C source program generating the corresponding DTLT_xxx.TXT output file. Most test output files simply represent a redirected and captured stdout stream. |
|
|
|
|
|
|
|
|
In a few instances, output to a file occurs within the test program. These exceptions are noted where they occur. |
|
|
|
|
|
|
|
|
You may use these files in several ways. Certainly, the test program source code should be compared to the output files. The output files may assist you in understanding details of usage. The test programs have been written in a deliberately simple and straight-forward way, with pedagogy a high priority, but the occasional detail or gem may escape a first reading. |
|
|
|
|
|