Hi John
I think you're right, and I need to place FPE 'brackets' around my
code.
The thing that was confusing me was that python has division by zero
exceptions (for which I assumed fenv.h was being used), but when from
python I reach down into my SWIG code and do a 1/0, no SIGFPE is
thrown.
I w
John Pye wrote:
> Hi John,
>
> On Jan 25, 3:43 pm, John Nagle <[EMAIL PROTECTED]> wrote:
>
>>Python is probably running with floating point exceptions disabled,
>>but you can enable them in your C code, and restoring the floating
>>point mode when you leave, if you want. This is probably
>>only
Hi John,
On Jan 25, 3:43 pm, John Nagle <[EMAIL PROTECTED]> wrote:
> Python is probably running with floating point exceptions disabled,
> but you can enable them in your C code, and restoring the floating
> point mode when you leave, if you want. This is probably
> only worth doing under a debug
John Pye wrote:
> Hi all
>
> I have some C code that is giving me some 'nan' values in some
> calculations. The C code is wrapped using SWIG to give me a Python
> module that I am then exercising through a unittest suite.
>
> It seems that I should expect the C code to throw floating point
> exc
Hi all
I have some C code that is giving me some 'nan' values in some
calculations. The C code is wrapped using SWIG to give me a Python
module that I am then exercising through a unittest suite.
It seems that I should expect the C code to throw floating point
exceptions (SIGFPE) and either the
