[Octave-bug-tracker] [bug #32242] incomplete initialisation of object arrays - follow up to bug #32222

[Volkmar Glauche]

Follow-up Comment #1, bug #32242 (project octave):

There seems to be a different behaviour in MATLAB and octave in this case,
which is handled in cfg_dep/subsasgn.m. In MATLAB, cfg_dep/subsasgn is called
with the following arguments:


>> dbstop @cfg_dep/subsasgn
>> d(2) = cfg_dep;
K>> whos
  Name          Size            Bytes  Class     Attributes

  dep           0x0                 0  double              
  subs          1x1               476  struct              
  varargin      1x1              2184  cell                


Here, dep is not yet classified, and more importantly, it is empty.

In Octave, the situation is different.


dbstop @cfg_dep/subsasgn
d(2) = cfg_dep;
debug> whos
Variables in the current scope:

  Attr Name          Size                     Bytes  Class
  ==== ====          ====                     =====  ===== 
   f   dep           1x1                          0  cfg_dep
   f   subs          1x1                         10  struct
   f   varargin      1x1                         12  cell
debug> dep
 
dep = 
 
cfg_dep object: 1-by-1

  scalar structure containing the fields:

    tname = [](0x0)
    tgt_exbranch = [](0x0)
    tgt_input = [](0x0)
    tgt_spec = [](0x0)
    jtsubs = [](0x0)
    sname = [](0x0)
    src_exbranch = [](0x0)
    src_output = [](0x0)


Here, dep is not empty, but the properties do not seem to be initialised by
the constructor code either. For MATLAB compatibility, dep should be empty
under these circumstances.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/