[Octave-bug-tracker] [bug #58953] Error with 'end' in index expression with nested function calls

[John W. Eaton]

Follow-up Comment #51, bug #58953 (project octave):

Thanks for the additional patch and tests.  I also see that it now appears to
work, but I'm having trouble understanding why it is appropriate to call
tree_evaluator::evaluate_end_expression in tree_identifier::evaluate_n when
the identifier is "end".  Is that always true?  Why?  Are there any other
cases that could result in this code path but not be the correct thing to do? 
I'm afraid that without understanding or being explicit here about what it
happening, that some future change will again result in introducing a bug or
at least additional confusion.

    _______________________________________________________

Reply to this item at:

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

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