[Octave-bug-tracker] [bug #61565] nchoosek broken for integer inputs

[Arun Giridhar]

Follow-up Comment #9, bug #61565 (project octave):

That is even better if Matlab returns an integer. I was basing my statement on
what I read in this bug report about nchoosek:
https://savannah.gnu.org/bugs/index.php?61199#comment25

Could you please check Matlab whether it warns of precision for values more
than flintmax? If not, that can be removed or changed from nchoosek too. Good
tests are: nchoosek (60, 30) gives a value above flintmax but less than 2^64,
so passing both inputs as uint64 will help. Another is nchoosek (80, 40) which
is well above 2^64, so any precision warning should be triggered in Matlab.

    _______________________________________________________

Reply to this item at:

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

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