[Octave-bug-tracker] [bug #61788] arrays of type int16 contain wrong numbers

[John W. Eaton]

Follow-up Comment #18, bug #61788 (project octave):

Sorry for the delay, I had hoped to fix this problem by now.

What I would like to do:

0 Eliminate all range objects from Octave and have the colon operator syntax
always produce vectors of the appropriate type.
0 Handle "for var = colon_expression ... end" syntax as a special case so that
the colon expression in this case does not produce a vector.
0 Preserve but deprecate the old Range class so that external code that uses
it can continue to work for some time.  But the "octave_value (const Range&)"
constructor would convert the Range object to a vector because Octave itself
would no longer handle Range objects internally.
0 Preserve enough of the old octave_range octave_value type so that loading
old data files will work.  But instead of creating range objects in Octave,
they would be converted to vectors when they are loaded.

But all of that is probably too much to do this late in the release process.

I've also considered doing all of the above except for ranges of double
precision floating point numbers (the only type of range supported by previous
versions of Octave) but having that one range type as a special case seems
even worse to me.

So, another option for the release is to revert the changes that introduced
the new range types and then work on making the changes outlined above in the
next major release of Octave.

    _______________________________________________________

Reply to this item at:

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

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