[Octave-bug-tracker] [bug #54562] numel should warn if the resulting double might be inaccurate

[Rik]

Update of bug #54562 (project octave):

                Severity:              3 - Normal => 1 - Wish               
                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #3:

I agree on a couple of points.  First, Octave's handling of very large indices
needs to be better.  Second, the problem can be broken up in to different
regimes where, unfortunately, Octave is performing poorly each time.  For
indices greater than intmax, as Dan has pointed out, the integer value
reverses sign and becomes negative and is generally handled poorly.  That is
the first thing to fix.  The second regime is indices greater than flintmax
but less than intmax where there can be a loss of precision.  A warning about
using linear indexing in this regime would be a good idea.  In addition, to
warning about linear indexing it should suggest the alternative of using full
subscripts (A(i,j)) which very likely preserves full precision.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54562>

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