Re: exception handling complex elementary functions (fwd)

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

Hi,
I've done as requested.   I decided not to use exact same format as
specfunc/error.h so the returned result is always similar to that of the
original functions.  Attached are complex\math.c (with some #ifndef
additions) and complex\math_eh.c.  Please let me know if you have any
other requests.

Thanks,
Andrew Binkley

On Wed, 7 Jan 2004, Brian Gough Wrote:
>Could you
>
> -- put the new functions in a separate file math_eh.c, so I don't need
> to put them directly in the existing file -- it is easier for
> maintenance that way.  Run the new file through indent to bring it
> into line with the GNU coding conventions.
>
> -- move the definitions in complex_math_eh.h into this file math_eh.c
> (there is no need for a separate header file in this case).
>
> -- It would be good practice to write these macros with arguments
> rather than using the various variable names implicitly in the
> definition.
>
> -- The macros are not exported so they do not need a GSL_COMPLEX
> prefix.  See the first definition in specfunc/error.h for an example
> of how it is done in the special functions.
>
> I'll deal with the configure script issues, such as testing whether
> the floating-point exception handling functions are available.
>
> Thanks,
>
> --
> Brian Gough
>

Attachment: math.c
Description: complex/math.c

Attachment: math_eh.c
Description: complex/math_eh.c