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

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

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


From: Arun Giridhar
Subject: [Octave-bug-tracker] [bug #61300] integer range might exceed upper limit
Date: Mon, 29 Nov 2021 15:08:01 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0

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

@Markus in comment #36: I think the denominator in Range.h should only say
m_increment not m_increment.value().

If I understand this class architecture, the base version will work for any
type T, but the integer-specialized ones will call foo.value() while the float
version and double version will process NaN etc first. So if we are passing
raw C++ integer values (not Octave integer values), which one is called? The
base version? I take it that is not possible from an end-user M-file?

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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