Re: exception handling complex elementary functions (fwd)

[Andrew Binkley <abinkley at cs dot toronto dot edu>]

Brian,
I have changed the format.  However, I ran into a small difficulty.  To
test the code fully, it is necc. to run cases where the machine overflows.
Subsquent tests behave in a strange fashion -- not entering the correct
blocks in gcov for instance (hence my earlier gcov question).

To get the correct results and, to fully test the code, the tests need to
be run one by one.  Assume that test.out is the executable that excersises
the code.  If test.out tests multiple cases, the results may be incorrect.
Instead what is required is that test.out only tests one result each time
it is run.

I think that this may pose a problem for the GSL testing system (not
sure).  If you get different results from the ones in my file when you
test, or the coverage in gcov is not complete, I think this is the most
likely explanation.  I had to do the tests one by one.  The composite gcov
covers all the code.

Hope this helps,
Andrew




On Fri, 16 Jan 2004, Brian Gough wrote:

> Andrew Binkley writes:
>  > Here are the test cases.  They should excercise all portions of the code.
>  > I had to redo the log ones -- thus the delay in my reply.  I am not
>  > familiar with the test suite so I have just included the cases in plain
>  > text.
>
> Hello,
>
> To add tests by hand to the test suite what you need to do is make a
> file results_eh.h containing lines like
>
>   {FN (sqrt), ARG(0.0e+00,0.0e+00), RES(0e0, 0.0)},
>
> where FN is the function (without the gsl_complex prefix), ARG is the
> argument and RES is the result.  Then #include this file in test.c
> immediately after the line where the existing results.h file is
> included.
>
> --
> Brian
>

Attachment: results_eh.h
Description: results_eh.h