[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-patch-tracker] [patch #9875] Wrong results from the mod() functi
|
From: |
Mike Miller |
|
Subject: |
[Octave-patch-tracker] [patch #9875] Wrong results from the mod() function for some range of integers |
|
Date: |
Wed, 20 Nov 2019 16:15:40 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36 |
Update of patch #9875 (project octave):
Status: None => Duplicate
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Thank you for the example, but this does not look like a patch submission,
there is no change proposed or attached.
However, this has already been raised and discussed as a bug report, so I'm
closing this as a duplicate of bug #35680.
Octave does not have arbitrary precision, if you want to calculate with
arbitrary precision then you might be interested in the symbolic package and
the vpa function. With vpa, I get the results that you seem to expect.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/patch/?9875>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/