[Octave-bug-tracker] [bug #55238] Modulo [mod(X, Y)] of larger values seems to fail silently to output 0

[Michael Leitner]

Follow-up Comment #7, bug #55238 (project octave):

mod is not constrained to integer input, so flintmax is not the point. I would
expect also mod(100,pi) to be inaccurate in the last two digits, because most
probably mod in this case is equivalent to fmod, thus giving the result of
100-31*pi (which obviously suffers from extinction in the last places).

Or is the documentation to be understood literally and mod is special-cased
only for integer types and not doubles that are integers, so that also in the
most common use-case mod falls back to fmod? Then the problem would be even
more severe.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55238>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/