[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, 14 Sep 2020 15:27:01 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

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

The more I look at this, the more complicated it appears to be, which leads me
to think that I'm missing something that could make the implementation much
simpler.  For example, what happens for expressions like


etc.  Are these (conceptually) equivalent to


?  If I understand correctly, evaluation of the partial expression for the
call to feval would result in one subsref call and the outer expression would
be another, with all arguments passed to that subsref evaluation.

I think that is all easy to fix now, but the thing that escapes me is how to
handle the following two cases differently:


I'm guessing there is some "natural" way of making this happen (especially if
TMW is basically admitting that this "feature" is an accident of their
implementation) but I'm not seeing it.

Given that any solution to this problem is likely to be disruptive, I think it
is best to abandon any attempt to fix it on stable and instead try to fix for
the next major release from the default branch.


Reply to this item at:


  Message sent via Savannah

reply via email to

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