[Octave-bug-tracker] [bug #46852] error gripe appearing when it seemingly shouldn't during length()

[Dan Sebald]

Follow-up Comment #4, bug #46852 (project octave):

I found the problem: programmer error.  "length" was assigned a value within
the function so had become a variable rather than a function call.  So, "not a
bug", and I should have caught that earlier.  However, I would say the error
message could be enhanced pretty easily by checking after this type of
indexing error whether the variable in question also appears in the function
table.  If so, print out "The function XYZ may have been redefined."

Note the slightly unusual behavior of the check in the sense that something
like

octave:102> ls = 1;
octave:103> ls ('testingwithu')
error: ls(119): out of bound 1
octave:103> char(119)
ans = w

is flagging an error on a character in the middle of the character array when
one would think it should be the 't' already that causes a problem.


    _______________________________________________________

Reply to this item at:

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

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