[Octave-bug-tracker] [bug #33637] Misleading "invalid use of end" error message

[John W. Eaton]

Update of bug #33637 (project octave):

             Assigned to:                    None => jwe                    

    _______________________________________________________

Follow-up Comment #2:

Yes, but you'll get a similar result if you try to index an undefined variable
with an undefined variable:


octave:1> a(x)
error: 'x' undefined near line 1 column 3
error: evaluating argument list element number 1


The reason the complaint is about the index instead of the object that is
being indexed is because Octave evaluates the argument list first, then looks
up the symbol.

However, for the end keyword, we have to first determine the value of the
object that is being indexed, so we can determine what "end" means.

So I suppose we could error at that point with a message that says the object
is invalid.  I'll try to take a look at this.

    _______________________________________________________

Reply to this item at:

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

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