[Octave-bug-tracker] [bug #61199] Allow 'char' input sets to nchoosek for Matlab compatibility

[anonymous]

Follow-up Comment #23, bug #61199 (project octave):

Could someone please check if Matlab gives integers beyond flintmax, like
nchoosek (64,32)? Where does Matlab start issuing warnings about accuracy?

Test for comment #21:


>> format long g

>> nchoosek (100,13)  ## NO PATCH, GETS WARNING, RESULT SLIGHTLY OFF
warning: nchoosek: possible loss of precision
warning: called from
    nchoosek at line 118 column 7

ans = 7110542499799197


>> nchoosek (100,13) ## PATCH, NO WARNING, RESULT EXACT
ans = 7110542499799200


Please compare with Matlab for presence of warnings and exactness.


    _______________________________________________________

Reply to this item at:

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

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