[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uin
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64 |
Date: |
Tue, 30 Nov 2021 13:19:46 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Follow-up Comment #9, bug #61132 (project octave):
If I understand correctly, the only cases that need special treatment are when
the base and limit are unsigned integers (of the same type) and the increment
is a negative double value. If so, then maybe we could limit this special
handling of "reverse" ranges to those unsigned integer ranges only and have
the signed integer and floating point ranges always defined with the "reverse"
flag set to false?
We never had integer ranges before, so saving and loading those shouldn't be a
compatibility issue.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61132>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, John W. Eaton, 2021/11/26
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, Markus Mützel, 2021/11/30
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64,
John W. Eaton <=
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, Arun Giridhar, 2021/11/30
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, Markus Mützel, 2021/11/30
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, Markus Mützel, 2021/11/30
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, Arun Giridhar, 2021/11/30
- [Octave-bug-tracker] [bug #61132] Colon operator fails for int64 and uint64, Arun Giridhar, 2021/11/30