[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58953] Error with 'end' in index expression w

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #58953] Error with 'end' in index expression with nested function calls
Date: Mon, 21 Sep 2020 14:17:12 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]