[Octave-bug-tracker] [bug #61300] integer range might exceed upper limit

[Markus Mützel]

Follow-up Comment #14, bug #61300 (project octave):

I'm not sure if this is the right way to fix this. IIUC, the whole point of
introducing integer type ranges was to correctly support ranges above
flintmax.
Would that still be working correctly when we cast to `double`?

Could we instead use the `value ()` function of the octave_int type to get the
underlying C++ type value? IIUC, C++ arithmetic would do the right thing in
this case.

    _______________________________________________________

Reply to this item at:

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

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