[Octave-bug-tracker] [bug #42651] Incorrect input validation for strings

[John W. Eaton]

Follow-up Comment #1, bug #42651 (project octave):

Maybe it doesn't make sense, but I prefer to use string_value followed by
checking for an error in case there is an octave_value type that can
legitimately be converted to a string.

The automatic conversion from numbers to strings was done for what I thought
was compatibility with Matlab.  But maybe that's no longer needed, or at least
not in as many places.  I do know that it is needed for things like


[ 65:67, '123' ]


but maybe what we should do is just change the way string_value works for
numeric classes, and force the conversions to happen where necessary for
compatibility?  I think that would mean fewer places that need to be changed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42651>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/