[Octave-bug-tracker] [bug #46571] classdef numel method not consulted for cell-indexed assignment

[Mike Miller]

Update of bug #46571 (project octave):

                 Summary: Inconsistency between old and new oop syntax (wrt
subsasgn) => classdef numel method not consulted for cell-indexed assignment

    _______________________________________________________

Follow-up Comment #3:

Dug into this a bit further, and confirmed that the error is that the numel
method is not consulted when Octave is trying to figure out how many values
need to be on the left and right of the assignment operator in an indexing
expression. Since the inconsistency is detected solely through calling the
numel method, the class subsasgn is never even called.

Octave expects types to define a numel function that returns the appropriate
number of elements that would be indexed given an indexing argument. This is
done correctly for old-style classes but not classdef classes.

Therefore, as assignment like `a{'v1'} = ones (10, 1)` is assumed to be
assigning to 2 elements of a cell-array-like thing.

    _______________________________________________________

Reply to this item at:

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

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