[Octave-bug-tracker] [bug #45507] acos returns different results on big input values

[Hartmut]

Follow-up Comment #5, bug #45507 (project octave):

I have tested the current default branch with this patch (from comment #4).
Here are my results for the acos function:

acos(1e7) = 0 + 16i
acos(1e8) = 0 + 19i

So the results still have the same sign in the imaginary part as Matlab (and
as Octave 4.0.0 release) = good.

The results don't have the jump to NaN values somewhere between 1e7 and 1e8
any more, which is similar to what Matlab does (and what Octave 3.8.2 release
did) = good.

But the results are still slightly different to Matlab: The imaginary part
seems to always be INTEGER valued, and not floating point valued. Is this
intended?



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45507>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/