[Numpy-discussion] Apropos ticked #913
Wed Mar 4 23:48:38 CST 2009
On Wed, Mar 4, 2009 at 23:32, Charles R Harris
> One thing that still bothers me a bit is the return value of fmax/fmin when
> comparing two complex nan values. A complex number is a nan whenever the
> real or imaginary part is nan, and currently the functions return such a
> number but originally they returned a complex number with both parts set to
> nan. The current implemetation was a compromise that kept the code simple
> while never explicitly using a nan value, i.e., the nan came from one of the
> inputs. I avoided the explicit use of a nan value because the NAN macro was
> possibly unreliable at the time. I'm open to thoughts on what the behavior
> should be.
Do we have examples from other implementations?
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco
More information about the Numpy-discussion