[Octave-bug-tracker] [bug #59704] function call on classdef subobject fails with "numel: invalid return value"

[Fernando]

Follow-up Comment #12, bug #59704 (project octave):

I think a good solution is to apply both patches proposed:

- Patch from comment #4 (file #50583). In octave_classdef::xnumel(),
temporarily set to null the left-value list of the current statement before
calling a user-defined numel method. This patch alone is enough to fix the
test case from comment #1. It does not affect sentences where numel is called
explicitly, such as

n=o.numel();

because in this case the call to numel is not done through
octave_classdef::xnumel.

- Patch from comment #9 (file #50634). Narrow the scope in which the lvalue
list of the sentence is considered by the tree_evaluator. This fixes the
problem with overloaded subsasgn mentioned in comment #6.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Mensaje enviado vía Savannah
  https://savannah.gnu.org/