octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #61199] Allow 'char' input sets to nchoosek fo


From: anonymous
Subject: [Octave-bug-tracker] [bug #61199] Allow 'char' input sets to nchoosek for Matlab compatibility
Date: Fri, 24 Sep 2021 01:10:05 -0400 (EDT)
User-agent: Mozilla/5.0 (Android 11; Mobile; rv:92.0) Gecko/92.0 Firefox/92.0

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

Hello,

I made some changes to the binomil coefficient calculation part of nchoosek so
that it returns exact integers all the way to flintmax and optionally up to
2^64‐1. Could someone verify if nchoosek (54,27) and nchoosek (56,28) give
warnings of loss of precision in Matlab please? Is there is interest in
extending the range of exactness for Octave or is it a Matlab compatibility
issue?  

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]