[Octave-bug-tracker] [bug #46571] Inconsistency between old and new oop syntax (wrt subsasgn)

[Mike Miller]

Update of bug #46571 (project octave):

                  Status:                    None => Confirmed              
                 Release:                   4.0.0 => dev                    

    _______________________________________________________

Follow-up Comment #2:

Actually I think the error is occurring in the parser, but I am not sure why
it is triggered for new-style classes but not old-style classes.

With just a trivial class definition / constructor and no other methods
defined, this error occurs with classdef:


@someclass/someclass.m:

classdef someclass < handle
endclassdef

>> x = someclass;
>> x{'foo'} = 0
error: invalid assignment to cs-list outside multiple assignment


but not if the class is a struct-based old-style class:


@someclass/someclass.m:

function y = someclass ()
  y = class (struct (), "someclass");
endfunction

>> x = someclass;
>> x{'foo'} = 0
error: class cannot be indexed with {


In the first case, the error is caught when the parser is evaluating the
assignment expression. In the second case, the error is only because there is
no custom aubsasgn method defined.

You're right that it has something to do with interpreting the string index as
an array of multiple indices, but I'm not clear at the moment why it's not a
problem when the old class definition style is used.

    _______________________________________________________

Reply to this item at:

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

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