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: Markus Mützel
Subject: [Octave-bug-tracker] [bug #61300] integer range might exceed upper limit
Date: Mon, 29 Nov 2021 12:08:07 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36 Edg/96.0.1054.34

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

Re comment #31: Maybe it would make sense to add a warning if the input is
larger than flintmax. Like you wrote, it is very unlikely that anyone will
ever see this warning (unless accidentally). But that additional check
wouldn't cost much either, I'd guess.

Re comment #32: Afaict, we are currently instantiating the range<T> template
with float, double and octave_int<T> types. There is already a specialization
of the init method for float and double. I guess, we can also specialize for
all octave_int<T> types.
Is it possible to specialize a template with a template class in C++11? Or
would we need to repeat the same specialization for each octave_int<T> type?

    _______________________________________________________

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]