Results of running
Results of running

echo 0xffff |lib/qsastime/qsastime_testlib

in the top-level build tree.  The tests consist of tests 1 (verbose near JD
epoch), 2 (verbose near year epoch), 3 (verbose near MJD epoch), and 4
(non-verbose for every year between -5 million and + 5 million which is very
close to the complete possible range since going to +/- 6 million years
overflows the double MJD->base_day. For each of these tests, the dates
covered for every year are at least Jan 1, Feb 28, Feb 29, Mar 1, and Dec 31
for both the Julian and Gregorian cases.

These tests complete all my planned tests for the case where broken-down 
time (variety of dates within each year being tested) is the argument.  They
make all possible internal consistency checks of libqsastime as well as all
possible external comparisons with my_timegm (the inverse of gmtime),
gmtime, and strftime (which has similar functionality to the library's
strfMJD) for the particular combinations of dates/times being tested.

More tests are planned where a large number of time_t values will be the
argument rather than the above broken-down time arguments.  These additional
tests will consist of essentially the same tests sampled differently in
time.  This added time coverage is unlikely to turn up any problems but is
being done for completeness.


svn path=/trunk/; revision=9521

FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot,FreeScienceCommunity/PLPlot